Issue 31470: Py_Initialize documentation wrong (original) (raw)
Issue31470
Created on 2017-09-14 16:31 by Jim.Jewett, last changed 2022-04-11 14:58 by admin. This issue is now closed.
| Messages (2) | ||
|---|---|---|
| msg302179 - (view) | Author: Jim Jewett (Jim.Jewett) *  |
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) *  |
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 |
| 2022-04-11 14:58:52 | admin | set | github: 75651 |
| 2019-03-21 23:05:12 | cheryl.sabella | set | status: open -> closedsuperseder: Document functions safe to be called before Py_Initialize()nosy: + cheryl.sabellamessages: + resolution: duplicatestage: resolved |
| 2017-09-14 16:31:02 | Jim.Jewett | create |