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 ncoghlan
Recipients Suzumizaki, amaury.forgeotdarc, brett.cannon, eric.snow, ncoghlan, serhiy.storchaka, vstinner
Date 2014-02-03.13:14:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7d+QAAN23HZeM1+eJqj4P0WDKP-miwM3DqisHwjXLjuRw@mail.gmail.com>
In-reply-to <1391431166.71.0.540702393679.issue20485@psf.upfronthosting.co.za>
Content
As Victor noted, inventing our own encoding scheme just for this use case
isn't desirable, although it's certainly a good fallback option that will
ensure the feature remains feasible even if trying to handle the Unicode
issues at the C compiler level proves too challenging.

The other aspect is that changes to the extension module initialisation API
always need to go into a PEP regardless, since we need to ensure such
changes are usable for both handwritten extensions and extension module
generators like Cython, cffi and SWIG.
History
Date User Action Args
2014-02-03 13:14:04ncoghlansetrecipients: + ncoghlan, brett.cannon, amaury.forgeotdarc, vstinner, Suzumizaki, eric.snow, serhiy.storchaka
2014-02-03 13:14:04ncoghlanlinkissue20485 messages
2014-02-03 13:14:04ncoghlancreate