This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jnoller
Recipients Thorney, bobbyi, gdb, jnoller, mattheww
Date 2011-01-19.14:22:07
SpamBayes Score 2.37275e-10
Marked as misclassified No
Message-id <>
In-reply-to <>
On Tue, Jan 18, 2011 at 6:23 PM, Brian Thorne <> wrote:
> Brian Thorne <> added the comment:
> With the example script attached I see the exception every time. On Ubuntu 10.10 with Python 2.6
> Since the offending line in multiprocesing/ (233) is a debug statement, just commenting it out seems to stop this exception.
> Looking at the util file shows the logging functions to be all of the form:
>    if _logger:
>        _logger.log(...
> Could it be possible that after the check the _logger global (or the debug function) is destroyed by the exit handler? Can we convince them to stick around until such a time that they cannot be called?
> Adding a small delay before joining also seems to work, but is ugly. Why should another Process *have* to have a minimum amount of work to not throw an exception?

See - but yes, the problem is that
the VM is nuking our imported modules before all the processes are
Date User Action Args
2011-01-19 14:22:10jnollersetrecipients: + jnoller, mattheww, Thorney, bobbyi, gdb
2011-01-19 14:22:07jnollerlinkissue4106 messages
2011-01-19 14:22:07jnollercreate