Changes by Kristján Valur Jónsson krist...@ccpgames.com:
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15365
___
___
Changes by Eric Snow ericsnowcurren...@gmail.com:
--
nosy: +eric.snow
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15365
___
___
Python-bugs-list
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset 54524897fafc by Kristján Valur Jónsson in branch 'default':
Issue #15365: Make traceback reporting ignore any errors when printing out
http://hg.python.org/cpython/rev/54524897fafc
--
nosy: +python-dev
Antoine Pitrou pit...@free.fr added the comment:
The patch looks simple enough, but you should use spaces, not tabs.
--
nosy: +amaury.forgeotdarc, pitrou
stage: - patch review
___
Python tracker rep...@bugs.python.org
Kristján Valur Jónsson krist...@ccpgames.com added the comment:
Certainly. But the submission filter would have caught that.
The question is: Is it acceptible to simply ignore errors from this api when
printing tracebacks? There are other errors that can be returned as well.
The trouble is,
Antoine Pitrou pit...@free.fr added the comment:
The trouble is, any errors in the traceback reporting will be ignored
anyway, since there is no way to report them :)
Which is a good reason to ignore them, isn't it? ;)
--
___
Python tracker
New submission from Kristján Valur Jónsson krist...@ccpgames.com:
Reporting an error early in the python startup, before importing is properly
initialized, can be tricky.
For example, here:
if (PyImport_ImportFrozenModule(_frozen_importlib) = 0) {
Py_FatalError(Py_Initialize: can't import
