>>> "Tim Peters" wrote > When the Zope3 tests are run under Python 2.3, after the test runner ends we > usually get treated to a long string of these things: > > """ > Unhandled exception in thread started by > Error in sys.excepthook: > Original exception was: > > """ Yep. I remember mentioning these at the Melbourne sprint. > I'm not sure what it says about Python's shutdown strategy. If I find and > fix a None-module-global problem in _Condition.wait(), that's fine and > probably helpful (in 2.3.1), but in the context of Zope3 the run() methods > of these threads are going to trigger None-module-global problems of their > own. That can also be fixed. Hm. Is this serious enough a problem to hold off 2.3.1 until it's fixed? My feeling is "no", because it only affects Z3 developers, and they're hardened to random pain by now, and it's also just a shutdown glitch. On the other hand, making the Z3 shutdown code os.kill(os.getpid(), 9) would also make the messages go away ;) Anthony -- Anthony Baxter <anthony at interlink.com.au> It's never too late to have a happy childhood.
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