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 Arfrever, Gregory.Andersen, amaury.forgeotdarc, franck, georg.brandl, lemburg, ncoghlan, pitrou, serhiy.storchaka, skrah, stutzbach, vstinner
Date 2013-01-24.20:42:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1359060128.98.0.922534694089.issue10156@psf.upfronthosting.co.za>
In-reply-to
Content
Serhiy's general approach here looks good to me (although there seem to be some unrelated changes to the re module in the current 3.2 patch).

For PEP 432, I want to try to rearrange things so that _PyUnicode_Init is one of the *first* calls made in Py_BeginInitialization (even before the general call to Py_ReadyTypes), but that still won't invalidate the work done here.
History
Date User Action Args
2013-01-24 20:42:09ncoghlansetrecipients: + ncoghlan, lemburg, georg.brandl, amaury.forgeotdarc, pitrou, vstinner, stutzbach, Arfrever, skrah, serhiy.storchaka, franck, Gregory.Andersen
2013-01-24 20:42:08ncoghlansetmessageid: <1359060128.98.0.922534694089.issue10156@psf.upfronthosting.co.za>
2013-01-24 20:42:08ncoghlanlinkissue10156 messages
2013-01-24 20:42:08ncoghlancreate