Christian Tismer wrote: > > "M.-A. Lemburg" wrote: > ... > > > Note that unicodedata is only needed by programs which do > > a lot of Unicode manipulations and in the future probably > > by some codecs too. > > Would it be possible to make the Unicode support configurable? This is currently not planned as the Unicode integration touches many different parts of the interpreter to enhance string/Unicode integration... sorry. Also, I'm not sure whether adding #ifdefs throuhgout the code would increase its elegance ;-) > 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. Why not ? All you have to do is rebuild the distribution every time you push a new version -- just like I did for the Unicode version before the CVS checkin was done. > 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 :-) -- Marc-Andre Lemburg ______________________________________________________________________ Business: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/
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