New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implementation of the PEP 587 #80944
Comments
I'm working on changes to complete the PEP-587, Python initiaization API. |
I updated my PEP-587: |
I closed the following issues which are fixed by the implementation of the PEP-587:
Copy of my message in bpo-19983: "This issue has been fixed by the PEP-587 in bpo-36763: when Py_Initialize() fails, it no longer calls abort() but only exit(1)." I should maybe document this change somewhere. In bpo-19983, I proposed a patch (init_error.patch) which changed the error message on initiallization error: "Python initialization error: %s\n" rather than "Fatal Python Error: xxx\n". Maybe we can change that? -- I close to leave bpo-22213 open. bpo-32573 (missing sys.argv) is already fixed in the master branch, but I have been asked to also fix the issue in Python 3.7, so I wrote PR 13553. |
TODO: I didn't implement PyWideStringList_Insert() yet. |
Two interesting TODO. sysmodule.c: get_xoptions()
sysmodule.c: get_warnoptions()
|
_PySys_ReadPreInitOptions() code should be moved somewhere closer to PyConfig_Read(). |
About the documentation: https://docs.python.org/dev/c-api/init.html doesn't link to http://docs.python.org/dev/c-api/init_config.html The first doc should mention somewhere the new doc. |
Another minor implementation issue: calling _PyCoreConfig_Read() twice calls _Py_SetArgcArgv() twice, the second call override the first _Py_SetArgcArgv() call. IMHO it should only be called once, at the first _PyCoreConfig_Read() call. |
Done in PR 15431. |
Done in PR 15433. |
I marked the PEP-587 Status as Final. The implementation should now be complete. If there are bugs, they can be fixed in following issues :-) I close now this issue. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: