Neal Norwitz wrote:
> So far it seems there isn't any specific problems with the approach.
> There are simply concerns. I not sure it would be best to modify this
> patch over many iterations and then make one huge checkin. I also
> don't want to lose the changes or the results. Perhaps I should make
> a branch for this work? It's easy to abondon it or take only the
> pieces we want if it should ever see the light of day.
A branch would seem the best way to allow other people to contribute to the
experiment.
I'll also note that this mechanism should make it easier to write C functions
which are easily used both from Python and as direct entries in a C API.
Cheers,
Nick.
--
Nick Coghlan | ncoghlan at email.com | Brisbane, Australia
---------------------------------------------------------------
http://boredomandlaziness.skystorm.net
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4