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 arigo, eric.snow, ncoghlan, njs, vstinner
Date 2019-02-26.01:03:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1551143039.1.0.196681158491.issue35886@roundup.psfhosted.org>
In-reply-to
Content
@Armin, thanks for fixing things on your end so quickly. :)

Adding PyInterpreterState.dict and a public getter function (a la PyThreadState) is probably fine.  I'm just not sure how that relates to the problem with cffi's use of the "builtins" field.  If it would be useful in general then feel free to open a separate issue.  I doubt there'd be much opposition if you presented a decent use case, since the cost would be low.

In the case of PyInterpreterState.builtins specifically, if you need it we could add a simple PyInterpreterState_GetBuiltins().  However, couldn't you already use existing public API, e.g. `PyEval_GetBuiltins()` or `PyImport_GetModule("builtins")`?  Regardless, we certainly don't want to put anyone in a position that they must define Py_BUILD_CORE just for access to PyInterpreterState fields.
History
Date User Action Args
2019-02-26 01:03:59eric.snowsetrecipients: + eric.snow, arigo, ncoghlan, vstinner, njs
2019-02-26 01:03:59eric.snowsetmessageid: <1551143039.1.0.196681158491.issue35886@roundup.psfhosted.org>
2019-02-26 01:03:59eric.snowlinkissue35886 messages
2019-02-26 01:03:59eric.snowcreate