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.
Created on 2013年07月19日 21:39 by vstinner, last changed 2022年04月11日 14:57 by admin. This issue is now closed.
| Messages (3) | |||
|---|---|---|---|
| msg193377 - (view) | Author: STINNER Victor (vstinner) * (Python committer) | Date: 2013年07月19日 21:39 | |
The import_init() function calls Py_FatalError() at any error. This is not kind for Py_NewInterpreter() which calls import_init(): Py_NewInterpreter() exits Python with a fatal error, instead of returning NULL, on import_init() failure. The pyfailmalloc tool can be used to easily inject faults (memory allocation failure) to test this issue: see issue #18408. import_init() should return an error instead of using Py_FatalError(). |
|||
| msg220627 - (view) | Author: Mark Lawrence (BreamoreBoy) * | Date: 2014年06月15日 12:25 | |
Just making sure this hasn't slipped under the radar. |
|||
| msg238418 - (view) | Author: STINNER Victor (vstinner) * (Python committer) | Date: 2015年03月18日 11:07 | |
This issue was more a reminder for myself (TODO list). I'm no more interested to work on the issue, so I just close it. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022年04月11日 14:57:48 | admin | set | github: 62707 |
| 2015年03月18日 11:07:14 | vstinner | set | status: open -> closed resolution: out of date messages: + msg238418 |
| 2014年06月15日 12:25:50 | BreamoreBoy | set | nosy:
+ BreamoreBoy messages: + msg220627 versions: + Python 3.5, - Python 3.4 |
| 2013年07月19日 21:39:11 | vstinner | create | |