cpython.git - https://github.com/python/cpython.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	convert usage of fail* to assert*	Benjamin Peterson	2009-06-30	1	-1/+1
\|
*	#Issue3088 in-progress: Race condition with instances of classes derived ↵	Amaury Forgeot d'Arc	2008-06-30	1	-0/+26
\| \| \| \| \| \| \| \| \| \| \| \| \|	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.
*	Update for threading.local test.	Christian Heimes	2008-01-19	1	-2/+18
\|
*	Added unit test to verify that threading.local doesn't cause ref leaks. It ↵	Christian Heimes	2008-01-19	1	-1/+27
\| \| \| \|	seems that the thread local storage always keeps the storage of the last stopped thread alive. Can anybody comment on it, please?
*	Standardize on test.test_support.run_unittest() (as opposed to a mix of ↵	Collin Winter	2007-04-25	1	-1/+1
\| \| \| \|	run_unittest() and run_suite()). Also, add functionality to run_unittest() that admits usage of unittest.TestLoader.loadTestsFromModule().
*	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