You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
import_init() should not use Py_FatalError() but return an error #62707
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:
assignee=Noneclosed_at=<Date2015-03-18.11:07:14.555>created_at=<Date2013-07-19.21:39:11.794>labels= ['type-feature']
title='import_init() should not use Py_FatalError() but return an error'updated_at=<Date2015-03-18.11:07:14.553>user='https://github.com/vstinner'
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 bpo-18408.
import_init() should return an error instead of using Py_FatalError().
Activity
vstinner commentedon Jul 19, 2013
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 bpo-18408.
import_init() should return an error instead of using Py_FatalError().
BreamoreBoy commentedon Jun 15, 2014
Just making sure this hasn't slipped under the radar.
vstinner commentedon Mar 18, 2015
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.