Martin v. Löwis wrote:
> M.-A. Lemburg wrote:
>
>>I think we should remove the defaulting to whatever
>>TCL uses and instead warn the user about a possible
>>problem in case TCL is found and uses a Unicode
>>width which is incompatible with Python's choice.
>
> -1.
Martin, please reconsider... the choice is between:
a) We have a cross-platform default Unicode width
setting of UCS2.
b) The default Unicode width is undefined and the only
thing we can tell the user is:
Run the configure script and then try the interpreter
to check whether you've got a UCS2 or UCS4 build.
Option b) is what the current build system implements
and causes problems since the binary interface of the
interpreter changes depending on the width of Py_UNICODE
making UCS2 and UCS4 builds incompatible.
I want to change the --enable-unicode switch back to
always use UCS2 as default and add a new option value
"tcl" which then triggers the behavior you've added to
support _tkinter, ie.
--enable-unicode=tcl
bases the decision to use UCS2 or UCS4 on the installed
TCL interpreter (if there is one).
--
Marc-Andre Lemburg
eGenix.com
Professional Python Services directly from the Source (#1, May 10 2005)
>>> 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
