On 2/17/06, M.-A. Lemburg <[EMAIL PROTECTED]> wrote: > Neal Norwitz wrote: > > > > I don't have a strong opinion. Any one else have an opinion about > > removing --with-wctype-functions from configure? > > FWIW, I announced this plan in Dec 2004: > > http://mail.python.org/pipermail/python-dev/2004-December/050193.html > > I didn't get any replies back then, so assumed that no-one > would object, but forgot to add this to the PEP 11. > > The reason I'd like to get this removed early rather than > later is that some Linux distros happen to use the config > switch causing the Python Unicode implementation on those > distros to behave inconsistent with regular Python > builds.
Like I said I don't have a strong opinion. At least update PEP 11 now. It would be good to ask on c.l.p. I suspect that no one cares enough about this flag to complain. So it's probably ok to remove it. But we should at least give people the opportunity to object. > Another candidate for removal is the --disable-unicode > switch. > > We should probably add a deprecation warning for that in > Py 2.5 and then remove the hundreds of > #idef Py_USING_UNICODE > from the source code in time for Py 2.6. I've heard of a bunch of people using --disable-unicode. I'm not sure if it's curiosity or if there are really production builds without unicode. Ask this on c.l.p too. We can update configure to add the warning and add a note to PEP 11. If we don't hear any complaints remove it for 2.6. If there are complaints, we can always back off. n _______________________________________________ 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
