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 Jim.Jewett
Recipients Jim.Jewett, docs@python
Date 2017-09-14.16:31:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1505406662.03.0.797586512068.issue31470@psf.upfronthosting.co.za>
In-reply-to
Content
Per https://docs.python.org/3/c-api/init.html#initializing-and-finalizing-the-interpreter Py_Initialize() "should be called before using any other Python/C API functions; with the exception of Py_SetProgramName(), Py_SetPythonHome() and Py_SetPath()."


(1)  I suspect that should be either Py_Initialize() or Py_InitializeEx().

(2)  Other functions can also be called first.  The ones I notice are:
(2a)  Py_IsInitialized() wouldn't be useful if you couldn't call it first.
(2b)  Py_SetStandardStreamEncoding explicitly says it *should* be called before Py_Initialize, if it is called at all.



(Probably applies to earlier python versions as well.)
History
Date User Action Args
2017-09-14 16:31:02Jim.Jewettsetrecipients: + Jim.Jewett, docs@python
2017-09-14 16:31:02Jim.Jewettsetmessageid: <1505406662.03.0.797586512068.issue31470@psf.upfronthosting.co.za>
2017-09-14 16:31:01Jim.Jewettlinkissue31470 messages
2017-09-14 16:31:01Jim.Jewettcreate