| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
| |
fixes local subclasses leaving old state around after a ref cycle GC which
could be recycled by new locals
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
from threading.local:
When a thread touches such an object for the first time, a new thread-local __dict__ is created,
and the __init__ method is run.
But a thread switch can occur here; if the other thread touches the same object, it installs another
__dict__; when the first thread resumes, it updates the dictionary of the second...
This is the deep cause of the failures in test_multiprocessing involving "managers" objects.
Also a 2.5 backport candidate.
|
| |
|
|
|
|
| |
seems that the thread local storage always keeps the storage of the last stopped thread alive. Can anybody comment on it, please?
|
|
|
|
| |
run_unittest() and run_suite()). Also, add functionality to run_unittest() that admits usage of unittest.TestLoader.loadTestsFromModule().
|
| |
|
|
http://mail.python.org/pipermail/python-dev/2004-June/045785.html
|