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:43:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
What is the level of impact of the callback problem?  Of the 4 scenarios in [1], it seems to me like #1 (C callbacks w/o a module reference) would be the most common.  However, can't that be addressed by adjusting the API, so it would only be a big problem in the case of a public C-API for the module (where backward-compatibility is a concern)?  #3 (classes have no reference to the module) sounds like the most problematic but how common a problem is it practice?

It may be worth including an explicit note in the multi-phase section on the scenarios that currently don't lend themselves well to multi-phase initialization.  It would also be great to indicate how to work around those issues (or the cases where for now it's better to just use single-phase initialization).

FWIW, the matter ties in directly to the work I'm doing with subinterpreters right now.

Date User Action Args
2015-07-03 17:43:02eric.snowsetrecipients: + eric.snow, brett.cannon, ncoghlan, petr.viktorin, docs@python, python-dev
2015-07-03 17:43:02eric.snowsetmessageid: <>
2015-07-03 17:43:02eric.snowlinkissue24458 messages
2015-07-03 17:43:02eric.snowcreate