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

Martin v. Löwis report at bugs.python.org
Sat Sep 4 19:29:42 CEST 2010


Martin v. Löwis <martin at v.loewis.de> 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 supposed to happen. The exitfuncs are called
*before* any other interpreter shutdown happens.

> 
> The old monkey patch can be found here:
> http://svn.python.org/view/python/tags/r261/Lib/multiprocessing/util.py?revision=71601&view=markup
>
>  I am pretty sure that this is one way to trigger the issue but by
> itself not the root of the problem.

Indeed, this is not part of Python anymore, so we should remove it from
the discussion.

In any case, unless you can come up with a reproducible test case,
I'm closing this as "works for me".

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue9775>
_______________________________________


More information about the Python-bugs-list mailing list