classification
Title: Py_Initialize documentation wrong
Type: Stage: resolved
Components: Documentation Versions: Python 3.6
process
Status: closed Resolution: duplicate
Dependencies: Superseder: Document functions safe to be called before Py_Initialize()
View: 32124
Assigned To: docs@python Nosy List: Jim.Jewett, cheryl.sabella, docs@python
Priority: normal Keywords:

Created on 2017-09-14 16:31 by Jim.Jewett, last changed 2019-03-21 23:05 by cheryl.sabella. This issue is now closed.

Messages (2)
msg302179 - (view) Author: Jim Jewett (Jim.Jewett) * (Python triager) Date: 2017-09-14 16:31
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.)
msg338569 - (view) Author: Cheryl Sabella (cheryl.sabella) * (Python committer) Date: 2019-03-21 23:05
Issue 32124 changed the documentation to define the C functions that are safe to call before Py_Initialize.  I am going to close this with that as a superseder.  Please reopen this if that issue didn't address all the concerns.  Thanks!
History
Date User Action Args
2019-03-21 23:05:12cheryl.sabellasetstatus: open -> closed

superseder: Document functions safe to be called before Py_Initialize()

nosy: + cheryl.sabella
messages: + msg338569
resolution: duplicate
stage: resolved
2017-09-14 16:31:02Jim.Jewettcreate