"Brett C." <bac at OCF.Berkeley.EDU>: > Back in February, I tried to fix an issue of threads executed using > 'threading' that did not shut themselves down before the interpreter > started tearing down globals, the thread triggering an exception, > and then a new exception being raised while trying to report the > exception raised in the thread by accessing globals Seems to me the way to fix this sort of thing properly is to get rid of the need for explicitly clearing globals. Now that we have a garbage collector, is it really necessary any more? What would happen if we simply set sys.modules to None and then invoked the collector? Greg Ewing, Computer Science Dept, +--------------------------------------+ University of Canterbury, | A citizen of NewZealandCorp, a | Christchurch, New Zealand | wholly-owned subsidiary of USA Inc. | greg at cosc.canterbury.ac.nz +--------------------------------------+
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