New submission from STINNER Victor <vstin...@redhat.com>: It would help to document that calling Py_Initialize() twice in Python 3.7 now triggers a fatal error, whereas previous the second call did nothing. Document it at: https://docs.python.org/dev/whatsnew/3.7.html#changes-in-the-c-api
... Or should it be considered as a regression? -- My colleague Miro Hrončok reported a Python crash (SIGABRT) when running https://github.com/konlpy/konlpy test suite on Python 3.7: "Fatal Python error: _Py_InitializeCore: main interpreter already initialized" konlpy uses the JPype project, the bug is in JPype initialization function (it's a C extension): * https://github.com/originell/jpype/issues/331 * https://github.com/originell/jpype/pull/332 ---------- assignee: docs@python components: Documentation keywords: easy messages: 320175 nosy: docs@python, eric.snow, ncoghlan, ned.deily, vstinner priority: normal severity: normal status: open title: Calling Py_Initialize() twice now triggers a fatal error (Python 3.7) versions: Python 3.7 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33932> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
