Author vstinner
Recipients Mark.Shannon, brett.cannon, dino.viehland, eric.snow, fabioz, gregory.p.smith, lukasz.langa, vstinner
Date 2019-11-25.21:53:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1574718836.02.0.853795620277.issue38500@roundup.psfhosted.org>
In-reply-to
Content
Fabio: "I don't really see a problem in breaking the API in major releases (so, having access for it in the internal API but without a backwards-compatibility guarantee seems like a good fit for me)."

In Python, the internal C API now means that you have to define Py_BUILD_CORE_MODULE macro and include a special "internal/pycore_pystate.h" header file.

If you are fine with doing that in PyCharm, what is the purpose of this issue?

Do you mean in *internal* API or a *private* API? Private API is basically a public API with weaker backward compatibility warranties and with a "_" prefix (_Py, _PY prefix).
History
Date User Action Args
2019-11-25 21:53:56vstinnersetrecipients: + vstinner, brett.cannon, gregory.p.smith, fabioz, dino.viehland, lukasz.langa, Mark.Shannon, eric.snow
2019-11-25 21:53:56vstinnersetmessageid: <1574718836.02.0.853795620277.issue38500@roundup.psfhosted.org>
2019-11-25 21:53:56vstinnerlinkissue38500 messages
2019-11-25 21:53:55vstinnercreate