Stephen Kelly added the comment:
I found that if I build and run this code with Python 3, then I get a very
different backtrace.
KernelBase.dll!00007ff963466142() Unknown
python36_d.dll!Py_FatalError(const char * msg) Line 1457 C
python36_d.dll!PyEval_AcquireLock() Line 253 C
mn.exe!main(int argc, char * * argv) Line 22 C
[External Code]
The failure is
Py_FatalError("PyEval_AcquireLock: current thread state is NULL");
So, it is not clear to me what is incorrect about this code, but presumably I
have done something incorrect here?
----------
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue30060>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
