[issue9863] threading, signals, atexit: different execution with different versions

2010-09-15 Thread Corey Bertram
Corey Bertram added the comment: On second thought, i'll just move forward with this new expected behavior. I understand the design decision and why it was made here in regards to waiting for threads to shutdown before atexit kicks in. My intended use for atexit just no longer works in

[issue9863] threading, signals, atexit: different execution with different versions

2010-09-15 Thread Corey Bertram
Corey Bertram added the comment: let me preface this: I'm no expert on how this should be done ect... The goal here was to specifically not set daemon on the test_loop thread. In an actual app test_loop would perhaps need to shutdown cleanly (save state or what have you). That said,

[issue9863] threading, signals, atexit: different execution with different versions

2010-09-15 Thread Corey Bertram
New submission from Corey Bertram : my code works on python 2.6.2 and fails to work on python 2.6.5. What's going on here? import atexit, sys, signal, time, threading terminate = False threads = [] def test_loop(): while True: if terminate: print('stopp

[issue9863] threading, signals, atexit: different execution with different versions

2010-09-15 Thread Corey Bertram
Changes by Corey Bertram : -- nosy: cbertram priority: normal severity: normal status: open title: threading, signals, atexit: different execution with different versions type: behavior versions: Python 2.6 ___ Python tracker <http://bugs.python.