[issue18507] import_init() should not use Py_FatalError() but return an error

[STINNER Victor]

STINNER Victor added the comment:

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.

--
resolution:  -> out of date
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18507] import_init() should not use Py_FatalError() but return an error

[Mark Lawrence]

Mark Lawrence added the comment:

Just making sure this hasn't slipped under the radar.

--
nosy: +BreamoreBoy
versions: +Python 3.5 -Python 3.4

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18507] import_init() should not use Py_FatalError() but return an error

[STINNER Victor]

New submission from STINNER Victor:

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().

--
messages: 193377
nosy: brett.cannon, haypo, ncoghlan
priority: normal
severity: normal
status: open
title: import_init() should not use Py_FatalError() but return an error
type: enhancement
versions: Python 3.4

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com