Christian Walther added the comment: > Is the bug avoided if you import threading first and use it instead of thread?
Yes. The bug happens when the (first) import of threading and the call to Py_Finalize() happen in different threads. To reproduce the problem in pure Python, I therefore have to use thread instead of threading to create the secondary thread. (In the C++ application, it's created on the C++ side.) Has anyone checked if the solution I propose in the first post makes sense? _____________________________________ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1596321> _____________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
