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 chris.jerdonek
Recipients brett.cannon, chris.jerdonek, ezio.melotti, zach.ware
Date 2013-01-25.10:58:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I looked into this a bit.  It seems like this is because with the patch, the call to "loader.loadTestsFromModule(the_module)" inside regrtest comes before the try-finally:

whereas with the current code, the analogous test-loading code is part of and so is protected by the try-finally inside test_main().  Apparently, simply discovering/loading tests from is enough to modify threading._dangling (e.g. when finding the tests to pass to load_tests).

I'm not sure yet what the right solution is, but it doesn't seem like test discovery should have that side effect.  It could be because of how test_concurrent_futures is written, or because of certain initialization code in one of the modules it depends on.
Date User Action Args
2013-01-25 10:58:11chris.jerdoneksetrecipients: + chris.jerdonek, brett.cannon, ezio.melotti, zach.ware
2013-01-25 10:58:10chris.jerdoneksetmessageid: <>
2013-01-25 10:58:10chris.jerdoneklinkissue16968 messages
2013-01-25 10:58:10chris.jerdonekcreate