> Yeah. To force this problem (couldn't trigger it) I set everything to > None in threading and then tried this. It triggered the right error, > but the function registered with atexit also threw a fit. But that is a > forced error since atexit will do its thing before teardown, right? It better. :-) > Regardless, I will try to go through the code and see if there are any > other points during the shutdown the reference a global and see if there > is a way to solve it cleanly. Otherwise I guess people just need to > shutdown there threading instances properly. Note that None is also a global... :-( --Guido van Rossum (home page: http://www.python.org/~guido/)
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