New submission from Dan Mahn <dan.m...@digidescorp.com>: I have a python-based test script that creates a daemon thread. The foreground basically runs a loop of commands, while the daemon thread sends some UDP data on the network. To stop the script, I use Control-C. This is running under 64-bit Windows (Vista) with 64-bit Python.
This script was developed under Python version 3.0, and has been running fine with 3.1. I downloaded 3.2RC1 and noticed that the script does not exit with the typical Ctrl-C. I also tried 3.2RC2, which had the same effect. If I do not start the background thread, the test exits normally. If I use Python 3.1, but I don't set the daemon attribute on the background thread, the operation duplicates the problem. Therefore, I believe there is a problem with 3.2 handling of daemon threads. ---------- components: None messages: 128260 nosy: dmahn priority: normal severity: normal status: open title: No exit when daemon thread is running. type: behavior versions: Python 3.2 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue11166> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
