[issue16749] Fatal Python error: PyEval_RestoreThread: NULL tstate

[Leonardo DaVinci]

Leonardo DaVinci added the comment:

Terry,

I've tried installing on Mac at least 6 times and I still get error
messages. I'm dealing with Solidoodle with no success.

I have an appointment with a 3d Print Lab on Jan 3rd (50 miles away) to
help me resolve my issues.

Regards
Ciro

On Fri, Dec 28, 2012 at 5:07 PM, Terry J. Reedy <report at bugs.python.org>wrote:

>
> Terry J. Reedy added the comment:
>
> Antoine: do you know anything about this message?
> Fatal Python error: PyEval_RestoreThread: NULL tstate
> Is there a serious possibility that it could indicate a CPython error, as
> opposed to an extension author error? Could running Windows on Mac hardware
> make a difference?
>
> Leonardo: You should have quoted the full error message instead of making
> each person search the image.
>
> Also, Please don't quote entire messages in your replies (which means
> deleting them if replying with a mail program). They are already visible
> above your reply and constitute noise that makes scrolling in the web
> interface more tedious.
>
> We will likely close this, at least for now, because there is currently no
> basis for action on our part.
>
> 1. From years of experience with such reports, we can be fairly certain
> that the problem is with the third party extension code. It is known that
> such code can crash CPython if it misuses the C API. We cannot prevent that
> without adding unacceptible overhead.
>
> 2. If there is a bug in CPython, then to do anything, we would need either
> Python code or proper C code that causes the crash. The latter would likely
> require cooperation of the Solidoodle extension authors.
>
> For us to do anything, we need evidence in the form of (minimal) code we
> can run that there is a CPython bug.
>
> Retrying under OS X is a good idea.
>
> You could try testing the windows python installation with the test suite
> (python -m test.regrtest in a command window) but there are two problems
> when doing this with a user installation, as opposed to the test buildbots:
> there will be (expected) error boxes that you have to dismiss by hitting
> <enter>; and there will be a few reported errors that are not really errors
> in python itself.
>
> ----------
> nosy: +pitrou, terry.reedy
> title: Fatal Python Error -> Fatal Python error: PyEval_RestoreThread:
> NULL tstate
> versions: +Python 2.7
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <http://bugs.python.org/issue16749>
> _______________________________________
>

----------
status: pending -> open

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue16749>
_______________________________________