> This is a completely separate issue, though probably around just as > long, and like the popup problem its frequency changes over time. By > "hung" here I'm referring to cases where something must go wrong with > a test and/or its cleanup such that a python_d process remains > running, usually several of them at the same time. So I end up with a > bunch of python_d processes in the background (but not with any > dialogs pending), which eventually cause errors during attempts the > next time the same builder is used since the file remains in use.
This is what kill_python.exe is supposed to solve. So I recommend to investigate why it fails to kill the hanging Pythons. Regards, Martin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
