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 | vstinner |
| Date | 2019年05月27日.15:37:17 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1558971438.04.0.54054760545.issue36763@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
I closed the following issues which are fixed by the implementation of the PEP 587: * bpo-1195571 * bpo-11320 * bpo-13533 * bpo-14956 * bpo-19983 * bpo-29778 * bpo-30560 * bpo-31745 * bpo-33135 * bpo-34725 * bpo-36204 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. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019年05月27日 15:37:18 | vstinner | set | recipients: + vstinner |
| 2019年05月27日 15:37:18 | vstinner | set | messageid: <1558971438.04.0.54054760545.issue36763@roundup.psfhosted.org> |
| 2019年05月27日 15:37:18 | vstinner | link | issue36763 messages |
| 2019年05月27日 15:37:17 | vstinner | create | |