[PEAK] Re: setuptools test command generates exception after interpreter shutdown

[Nikolaus Rath]

On 05/04/2010 11:23 AM, P.J. Eby wrote:
> Now, to narrow it down further, we'll have to remove stuff from the
> setuptools code execution path to find out what part of setuptools is
> relevant.  I would start with removing code from the test command's
> 'run()' method, especially the running of other commands such as
> egg_info, and the saving and restoring of sys.path and sys.modules.  My
> guess at this point is that it may be the sys.modules restoration that
> triggers it.
> 
> Actually, there's a quick way to test that: add 'import multiprocessing,
> logging' to your setup.py (not the test code).  If that makes it work,
> then the sys.modules restoration is probably the culprit.  If it still
> doesn't work, then it's almost certainly a multiprocessing/logging bug.

Good guess, adding the import to setup.py indeed fixes the problem. Are
you able to do something about this? Or is that an intrinsic problem
with the restoration?


Best,

   -Nikolaus

-- 
 »Time flies like an arrow, fruit flies like a Banana.«

  PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6  02CF A9AD B7F8 AE4E 425C