On Wed, 15 Mar 2000, Christian Tismer wrote: >... > Would it be possible to make the Unicode support configurable? This might be interesting from the standpoint of those guys who are doing the tiny Python interpreter thingy for embedded systems. > My problem is that patches in the CVS are of different kinds. > Some are error corrections and enhancements which I would > definately like to use. > Others are brand new features like the Unicode support. > Absolutely great stuff! But this will most probably change > a number of times again, and I think it is a bad idea when > I include it into my Stackless distribution. > > I'd appreciate it very much if I could use the same CVS tree > for testing new stuff, and to build my distribution, with > new features switched off. Please :-) But! I find this reason completely off the mark. In essence, you're arguing that we should not put *any* new feature into the CVS repository because it might mess up what *you* are doing. Sorry, but that just irks me. If you want a stable Python, then don't use the CVS version. Or base it off a specific tag in CVS. Or something. Just don't ask for development to be stopped. Cheers, -g -- Greg Stein, http://www.lyra.org/
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