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 | vstinner |
|---|---|
| Recipients | docs@python, eric.snow, ncoghlan, ned.deily, vstinner |
| Date | 2018年06月21日.13:08:47 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
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 |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018年06月21日 13:08:48 | vstinner | set | recipients: + vstinner, ncoghlan, ned.deily, docs@python, eric.snow |
| 2018年06月21日 13:08:48 | vstinner | set | messageid: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za> |
| 2018年06月21日 13:08:48 | vstinner | link | issue33932 messages |
| 2018年06月21日 13:08:47 | vstinner | create | |