➜

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 ncoghlan
Recipients eric.snow, htgoebel, ncoghlan, ned.deily, pmpp, springermac, vstinner
Date 2018-03-21.13:06:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1521637595.52.0.467229070634.issue33042@psf.upfronthosting.co.za>
In-reply-to
Content 
Thinking about PySys_AddWarnOptionUnicode a little further, I'm not sure we actually need to change anything in the implementation there - I think we can just make it clearer in the docs that *only* PySys_AddWarnOption is supported prior to Py_Initialize for the embedding use case - the unicode version of the API currently only makes sense in CPython, where we can call it after _Py_InitializeCore.

It will make sense for embedding applications in 3.8 once we make Py_InitializeCore a public API.
History
Date User Action Args
2018-03-21 13:06:35ncoghlansetrecipients: + ncoghlan, htgoebel, vstinner, ned.deily, pmpp, eric.snow, springermac
2018-03-21 13:06:35ncoghlansetmessageid: <1521637595.52.0.467229070634.issue33042@psf.upfronthosting.co.za>
2018-03-21 13:06:35ncoghlanlinkissue33042 messages
2018-03-21 13:06:35ncoghlancreate