Author sbt
Recipients belopolsky, chris.jerdonek, mcdonc, python-dev, sbt
Date 2012-09-10.18:41:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1347302506.46.0.238881614726.issue15881@psf.upfronthosting.co.za>
In-reply-to
Content
I suspect the problem is caused by nose's isolate plugin.

With this enabled, a copy of sys.modules is saved before each test and then restored after the test.  This causes garbage collection of newly imported modules.  The destructor for the module type causes all globals to be replaced by None.

This will break the atexit function registered by multiprocessing since it depends on globals.

PS. A simple work-around (which does not require people to upgrade to a bugfixed version of Python) is to put

    try:
        import multiprocessing
    except ImportError:
        pass

near the beginning of setup.py.  After this change I don't get the error when running "python setup.py test".
History
Date User Action Args
2012-09-10 18:41:46sbtsetrecipients: + sbt, belopolsky, mcdonc, chris.jerdonek, python-dev
2012-09-10 18:41:46sbtsetmessageid: <1347302506.46.0.238881614726.issue15881@psf.upfronthosting.co.za>
2012-09-10 18:41:46sbtlinkissue15881 messages
2012-09-10 18:41:45sbtcreate