| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | #6990: clear threading.local's key only after its thread state is removed: | Philip Jenvey | 2009-09-29 | 1 | -1/+40 |
| | | | | | | | fixes local subclasses leaving old state around after a ref cycle GC which could be recycled by new locals (backported from r75123) | ||||
| * | #Issue3088 in-progress: Race condition with instances of classes derived ↵ | Amaury Forgeot d'Arc | 2008-07-01 | 1 | -0/+29 |
| | | | | | | | | | | | | | | 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. Backport of r64601. | ||||
| * | setUp and tearDown functions are now passed the test object | Jim Fulton | 2004-08-28 | 1 | -2/+2 |
| | | |||||
| * | Implemented thread-local data as proposed on python-dev: | Jim Fulton | 2004-07-14 | 1 | -0/+26 |
| http://mail.python.org/pipermail/python-dev/2004-June/045785.html | |||||
 |
index : cpython.git | |
| https://github.com/python/cpython.git |
| summaryrefslogtreecommitdiffstats |