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 vstinner
Recipients Decorater, eric.snow, ncoghlan, serhiy.storchaka, vstinner
Date 2017-11-23.00:29:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1511396985.98.0.213398074469.issue32096@psf.upfronthosting.co.za>
In-reply-to
Content
"Victor, I think you're fundamentally misunderstanding the goals of PEP 432. The entire point is to let people have a *mostly working Python runtime* during CPython startup. (...)"

While the PEP 432 is nice, all changes are currently done in private APIs, symbols starting with _Py. I would prefer that nobody uses these new APIs before the conversion is complete. And from what I saw, I can say that the conversion just started, there are still a lot of changes that should be done.

While having _PyRuntime.mem is nice to have in the long term, it doesn't add any value *right now*, except of making the existing C API harder to use.

I would prefer to do things in this order:

* Revert _PyRutime.mem
* Finish PEP 432 implementation
* Recreate _PyRutime.mem

Maybe we can complete these 3 steps before Python 3.7, but I'm not sure about that.
History
Date User Action Args
2017-11-23 00:29:46vstinnersetrecipients: + vstinner, ncoghlan, eric.snow, serhiy.storchaka, Decorater
2017-11-23 00:29:45vstinnersetmessageid: <1511396985.98.0.213398074469.issue32096@psf.upfronthosting.co.za>
2017-11-23 00:29:45vstinnerlinkissue32096 messages
2017-11-23 00:29:45vstinnercreate