This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author zooko
Recipients gvanrossum, lemburg, loewis, r.david.murray, scoder, stutzbach, vstinner, zooko
Date 2010-05-08.04:46:21
SpamBayes Score 2.68223e-05
Marked as misclassified No
Message-id <>
> Option 1: Make Unicode-agnosticism the default and force anyone who cares about the Unicode setting to include a separate header.  If they don't include that header, they can only call safe functions and can't poke at PyUnicodeObject's internals.  If they include the header, their module will always generate a link failure if the Unicode settings are mismatched.  (Guido proposed this solution in the python-ideas thread)


The packaging and compatibility problems are pressing concerns for many people. Poking at PyUnicodeObject's internals seems like a rare pretty rare need for an extension module to do. If I understand correctly, this option provides the best solution to the packaging and compatibility issues (over the long term, as Python and the authors of extension modules upgrade).
Date User Action Args
2010-05-08 04:46:31zookosetrecipients: + zooko, lemburg, gvanrossum, loewis, scoder, vstinner, stutzbach, r.david.murray
2010-05-08 04:46:28zookosetmessageid: <>
2010-05-08 04:46:24zookolinkissue8654 messages
2010-05-08 04:46:22zookocreate