[issue9775] Multiprocessing, logging and atexit play not well together

Georg Brandl added the comment: Not reproducable anymore. -- resolution: -> out of date status: open -> closed ___ Python tracker ___ ___

[issue9775] Multiprocessing, logging and atexit play not well together

Changes by R. David Murray : -- stage: -> unit test needed type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue9775] Multiprocessing, logging and atexit play not well together

Changes by Georg Brandl : -- assignee: -> georg.brandl priority: normal -> high versions: +Python 3.2 -Python 2.6 ___ Python tracker ___ _

[issue9775] Multiprocessing, logging and atexit play not well together

Georg Brandl added the comment: I'll sort this out with Armin. -- nosy: +georg.brandl ___ Python tracker ___ ___ Python-bugs-list mail

[issue9775] Multiprocessing, logging and atexit play not well together

Martin v. Löwis added the comment: I don't see the issue at all; the attached script runs just fine. -- Added file: http://bugs.python.org/file18754/t.py ___ Python tracker ___ _

[issue9775] Multiprocessing, logging and atexit play not well together

Armin Ronacher added the comment: Put the stuff from an older version back in with a monkeypatch and you will see the issue again. There are certainly many more ways to trigger that issue, that was just the easiest. I will try to create a simpler test case. -- resolution: works for

[issue9775] Multiprocessing, logging and atexit play not well together

Changes by Martin v. Löwis : -- resolution: -> works for me status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing

[issue9775] Multiprocessing, logging and atexit play not well together

Martin v. Löwis added the comment: > As mentioned above I cannot provide more information because I am > unable to find the root of the issue. All I know is that if the > atexit handler is executed after the module globals were set to None > it fails to shutdown properly. Ok - but this is not

[issue9775] Multiprocessing, logging and atexit play not well together

Armin Ronacher added the comment: This also affects 2.7, I just worked on 2.6 because this is where I encountered the issue. > As for 2.7: please try explaining again what specific issue the patch > is meant to resolve? What monkey-patching are you referring to? What > destructor? Why is alia

[issue9775] Multiprocessing, logging and atexit play not well together

Changes by Armin Ronacher : -- versions: +Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue9775] Multiprocessing, logging and atexit play not well together

Martin v. Löwis added the comment: IIUC, you are proposing to fix Python 2.6 only. Please understand that this branch is closed for bug fixes (unless they are security issues, which this issue is not). As for 2.7: please try explaining again what specific issue the patch is meant to resolve?

[issue9775] Multiprocessing, logging and atexit play not well together

Changes by Armin Ronacher : -- keywords: +patch Added file: http://bugs.python.org/file18746/9775-fix.patch ___ Python tracker ___ ___

[issue9775] Multiprocessing, logging and atexit play not well together

New submission from Armin Ronacher : It's hard to say what exactly is to blame here, but I will try to outline the problem as good as I can and try to track it down: A library of mine is using a Thread that is getting entries from a multiprocessing.Queue periodically. What I find when the pyt