Martin v. Löwis wrote: > M.-A. Lemburg wrote: >> I'd argue that such code is broken anyway: 3rd party code simply >> cannot make any assumptions on the typedef behind Py_UNICODE. > > The code would work just fine now, but will stop working with the > change. Users of the code might not be open to arguments.
Fair enough. Let's leave things as they are for 2.4, then. > In any case, it's up to the release manager to decide. > >> Note that you'd only see this change when compiling Python in the >> non-standard UCS4 setting on Linux. > > Sure. That happens to be the default on many Linux distributions, > though. Unfortunately, that's true. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 14 2006) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
