[Jeremy Hylton] > ... > So what's the right way to fix this test? If the test can't be run as > part of regrtest and can't be imported, I wonder why it's in Lib/test > to begin with. It runs fine if run as Guido suggested (from the cmdline). I just checked in(*) a change that causes it to punt if the import lock is held. This prevents running it via import (whether directly from a Python shell or indirectly via regrtest). test_threaded_import is the pioneer in these miserable cases, and I suppose test_socketserver could/should also be reworked to exploit test_threaded_import's test_main() trick too (then it should be able to run under regrtest, but still not via direct import). BTW, when large magical things happen as a side-effect of merely importing a module, we complain when the context is Zope <wink>. The "test_main() trick" breaks the connection between importing a test module and actually running the test. (*) But it hasn't completed -- lines and lines of cvs server: [12:27:14] waiting for anoncvs_python's lock in cvsroot/python/python/dist/src/Lib/test Hope we don't have an immortal lock again!
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4