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 eric.snow
Recipients brett.cannon, docs@python, eric.snow, ncoghlan, petr.viktorin, python-dev
Date 2015-07-03.17:42:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1435945350.19.0.922440589898.issue24458@psf.upfronthosting.co.za>
In-reply-to
Content
Sorry I didn't get a review in before.  Since subinterpreters and multi-phase initialization are on my mind, I have a couple questions:

Should there be a note in the "Single-phase initialization" section (perhaps at the top of the section) that encourages use of multi-phase initialization?

Would it be worth demonstrating how a module might be verified to work with subinterpreters (as indicated in the multi-phase section)?  An example with a brief main function would likely be sufficient.  If it's not obvious how to do it then module authors may not consider it worth the trouble.  If all goes well then subinterpreters will be exposed in Python in 3.6 which will make such testing much easier.
History
Date User Action Args
2015-07-03 17:42:30eric.snowsetrecipients: + eric.snow, brett.cannon, ncoghlan, petr.viktorin, docs@python, python-dev
2015-07-03 17:42:30eric.snowsetmessageid: <1435945350.19.0.922440589898.issue24458@psf.upfronthosting.co.za>
2015-07-03 17:42:30eric.snowlinkissue24458 messages
2015-07-03 17:42:29eric.snowcreate