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 eric.snow, htgoebel, miss-islington, ncoghlan, ned.deily, pmpp, springermac, vstinner
Date 2018-03-25.20:54:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1522011291.86.0.467229070634.issue33042@psf.upfronthosting.co.za>
In-reply-to
Content
Would it be possible to not officially allow calling PySys_AddWarnOption() before Py_Initialize()? Fix the bug, but don't promote doing that. I just suggest to revert:

Doc/c-api/init.rst:

+  * :c:func:`PySys_AddWarnOption`
+  * :c:func:`PySys_AddXOption`
+  * :c:func:`PySys_ResetWarnOptions`
History
Date User Action Args
2018-03-25 20:54:51vstinnersetrecipients: + vstinner, htgoebel, ncoghlan, ned.deily, pmpp, eric.snow, miss-islington, springermac
2018-03-25 20:54:51vstinnersetmessageid: <1522011291.86.0.467229070634.issue33042@psf.upfronthosting.co.za>
2018-03-25 20:54:51vstinnerlinkissue33042 messages
2018-03-25 20:54:51vstinnercreate