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-21.15:56:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1511279765.54.0.213398074469.issue32096@psf.upfronthosting.co.za>
In-reply-to
Content
IMHO for the long term, the best would be to have a structure for pre-Py_Initialize configuration, maybe _PyCoreConfig, and pass it to functions that can be called before Py_Initialize().

For example, I'm working on a variant of Py_GetPath() which accepts a _PyCoreConfig to be able to pass the value of the PYTHONPATH environment variable.

That's a more complex solution, so I proposed to first revert, to have more time to design the "correct API".
History
Date User Action Args
2017-11-21 15:56:05vstinnersetrecipients: + vstinner, ncoghlan, eric.snow, serhiy.storchaka, Decorater
2017-11-21 15:56:05vstinnersetmessageid: <1511279765.54.0.213398074469.issue32096@psf.upfronthosting.co.za>
2017-11-21 15:56:05vstinnerlinkissue32096 messages
2017-11-21 15:56:05vstinnercreate