Adam Olsen wrote:
On Sun, Sep 20, 2009 at 10:17, Zooko O'Whielacronx
wrote: On Sun, Sep 20, 2009 at 8:27 AM, Antoine Pitrou
wrote: AFAIK, C extensions should fail loading when they have the wrong UCS2/4 setting.
That would be an improvement! Unfortunately we instead get mysterious misbehavior of the module, e.g.:
http://bugs.python.org/setuptools/msg309 http://allmydata.org/trac/tahoe/ticket/704#comment:5
I agree that a better error message would help. I'm just not sure how to achieve that. The error message you currently see gets generated by the dynamic linker trying to resolve a Python Unicode API symbol: the API names are mangled to assure that you cannot mix UCS2 interpreters and UCS4 extensions (and vice-versa). We could try to scan the linker error message for 'Py.*UCS.' and then replace the message with a more helpful one (in importdl.c), but I'm not sure how portable that is. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Oct 08 2009)
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 our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/