summaryrefslogtreecommitdiffstats
path: root/Lib/threading.py
Commit message (Collapse)AuthorAgeFilesLines
* Fix Issue8262 - changing RuntimeError wording to "Threads can only be ↵Senthil Kumaran2010-04-061-1/+1
| | | | started once"
* Issue #7481: When a threading.Thread failed to start it would leave theGregory P. Smith2010-02-281-1/+6
| | | | instance stuck in initial state and present in threading.enumerate().
* No need to assign the results of expressions used only for side effects.Georg Brandl2010-02-061-1/+0
|
* Issue #7282: Fix a memory leak when an RLock was used in a thread otherAntoine Pitrou2009-11-091-8/+10
| | | | | than those started through `threading.Thread` (for example, using `thread.start_new_thread()`.
* Issue #7264: Fix a possible deadlock when deallocating thread-local objectsAntoine Pitrou2009-11-051-0/+4
| | | | which are part of a reference cycle.
* #7125: fix typo.Georg Brandl2009-10-141-3/+3
|
* fix Thread.ident when it is the main thread or a dummy thread #5632Benjamin Peterson2009-03-311-1/+6
|
* take the usual lock precautions around _active_limbo_lockBenjamin Peterson2009-03-311-21/+13
|
* #1674032: return value of flag from Event.wait(). OKed by Guido.Georg Brandl2009-03-311-0/+1
|
* Backport relevant part of r66274 (in issue #874900).Antoine Pitrou2008-09-061-2/+5
|
* remove py3k warnings about the threading api; update docsBenjamin Peterson2008-09-011-31/+21
| | | | Reviewer: Benjamin Peterson
* fix a few get_name() calls and turn then to .nameBenjamin Peterson2008-08-221-4/+4
| | | | Reviewer: Christian Heimes
* add py3k warnings for old threading APIsBenjamin Peterson2008-08-181-1/+11
| | | | they will still live in 3.0 but it can't hurt
* bring back the old APIBenjamin Peterson2008-08-181-0/+12
|
* backport threading property changesBenjamin Peterson2008-08-181-18/+12
|
* change threading.getIdent to a propertyBenjamin Peterson2008-08-181-1/+2
| | | | This is new in 2.6 so now need to worry about backwards compatibility :)
* Remove a tuple unpacking in a parameter list to suppress the SyntaxWarning withBrett Cannon2008-08-021-1/+2
| | | | -3.
* Apply patch for 874900: threading module can deadlock after forkJesse Noller2008-07-161-0/+31
|
* add old names back into __all__Benjamin Peterson2008-06-111-1/+2
|
* add aliases to threading moduleBenjamin Peterson2008-06-111-0/+32
|
* give the threading API PEP 8 namesBenjamin Peterson2008-06-111-35/+35
|
* Adds a Thread.getIdent() method to provide the _get_ident() value forGregory P. Smith2008-06-011-2/+10
| | | | any given threading.Thread object. feature request issue 2871.
* #1733757: the interpreter would hang on shutdown, if the function set by ↵Amaury Forgeot d'Arc2008-04-031-7/+8
| | | | | | | | | | | | sys.settrace calls threading.currentThread. The correction somewhat improves the code, but it was close. Many thanks to the "with" construct, which turns python code into C calls. I wonder if it is not better to sys.settrace(None) just after running the __main__ module and before finalization.
* Block the sys.exc_clear -3 warning from threading.py.Jeffrey Yasskin2008-03-311-0/+7
|
* Revert my experiment. I found one reason of failures in test_logging.Amaury Forgeot d'Arc2008-03-291-3/+1
|
* At least let the module compileAmaury Forgeot d'Arc2008-03-291-0/+1
|
* Try to understand why most buildbots suddenly turned to red.Amaury Forgeot d'Arc2008-03-291-1/+2
| | | | | | Undo the only change that might have unexpected effects. To be followed.
* Kill a race in test_threading in which the exception info in a thread finishingJeffrey Yasskin2008-03-281-0/+9
| | | | | | | up after it was joined had a traceback pointing to that thread's (deleted) target attribute, while the test was trying to check that the target was destroyed. Big thanks to Antoine Pitrou for diagnosing the race and pointing out sys.exc_clear() to kill the exception early. This fixes issue 2496.
* Thread.start() used sleep(0.000001) to make sure it didn't return before theJeffrey Yasskin2008-02-281-11/+10
| | | | | | | | | | | | | | | | | | | | | | new thread had started. At least on my MacBook Pro, that wound up sleeping for a full 10ms (probably 1 jiffy). By using an Event instead, we can be absolutely certain that the thread has started, and return more quickly (217us). Before: $ ./python.exe -m timeit -s 'from threading import Thread' 't = Thread(); t.start(); t.join()' 100 loops, best of 3: 10.3 msec per loop $ ./python.exe -m timeit -s 'from threading import Thread; t = Thread()' 't.isAlive()' 1000000 loops, best of 3: 0.47 usec per loop After: $ ./python.exe -m timeit -s 'from threading import Thread' 't = Thread(); t.start(); t.join()' 1000 loops, best of 3: 217 usec per loop $ ./python.exe -m timeit -s 'from threading import Thread; t = Thread()' 't.isAlive()' 1000000 loops, best of 3: 0.86 usec per loop To be fair, the 10ms isn't CPU time, and other threads including the spawned one get to run during it. There are also some slightly more complicated ways to get back the .4us in isAlive() if we want.
* Followup to r61011: Also avoid the reference cycle when the Thread's targetJeffrey Yasskin2008-02-231-5/+7
| | | | raises an exception.
* Prevent classes like:Jeffrey Yasskin2008-02-231-0/+3
| | | | | | | | | | | | | | class RunSelfFunction(object): def __init__(self): self.thread = threading.Thread(target=self._run) self.thread.start() def _run(self): pass from creating a permanent cycle between the object and the thread by having the Thread delete its references to the object when it completes. As an example of the effect of this bug, paramiko.Transport inherits from Thread to avoid it.
* Revert 60189 and restore performance.Raymond Hettinger2008-01-241-8/+24
|
* - Fix Issue #1703448: A joined thread could show up in theGregory P. Smith2008-01-221-5/+8
| | | | | threading.enumerate() list after the join() for a brief period until it actually exited.
* Replace spam.acquire() try: ... finally: spam.release() with "with spam:"Gregory P. Smith2008-01-221-24/+8
|
* Add a hack (originally devised in a slightly different form by Thomas Wouters)Guido van Rossum2007-08-201-0/+20
| | | | | to prevent spurious tracebacks when a daemon thread's cleanup happens to wake up when the world around it has already been destroyed.
* Eliminate RLock race condition reported in SF bug #1764059Nick Coghlan2007-07-311-1/+2
|
* Patch #1731049: make threading.py use a proper "raise" when checking ↵Collin Winter2007-06-061-12/+23
| | | | internal state, rather than assert statements (which get stripped out by -O).
* Bug #1566280: Explicitly invoke threading._shutdown from Py_Main,Martin v. Löwis2007-01-041-5/+5
| | | | | to avoid relying on atexit. Will backport to 2.5.
* Patch #1454481: Make thread stack size runtime tunable.Andrew MacIntyre2006-06-131-1/+3
| | | | | | | | | | Heavily revised, comprising revisions: 46640 - original trunk revision (backed out in r46655) 46647 - markup fix (backed out in r46655) 46692:46918 merged from branch aimacintyre-sf1454481 branch tested on buildbots (Windows buildbots had problems not related to these changes).
* Revert revisions:Tim Peters2006-06-041-3/+1
| | | | | | | | | | | | | | | | 46640 Patch #1454481: Make thread stack size runtime tunable. 46647 Markup fix The first is causing many buildbots to fail test runs, and there are multiple causes with seemingly no immediate prospects for repairing them. See python-dev discussion. Note that a branch can (and should) be created for resolving these problems, like svn copy svn+ssh://svn.python.org/python/trunk -r46640 svn+ssh://svn.python.org/python/branches/NEW_BRANCH followed by merging rev 46647 to the new branch.
* Patch #1454481: Make thread stack size runtime tunable.Andrew MacIntyre2006-06-041-1/+3
|
* Get rid of __context__, per the latest changes to PEP 343 and python-devGuido van Rossum2006-05-021-8/+5
| | | | | | | | discussion. There are two places of documentation that still mention __context__: Doc/lib/libstdtypes.tex -- I wasn't quite sure how to rewrite that without spending a whole lot of time thinking about it; and whatsnew, which Andrew usually likes to change himself.
* Implement MvL's improvement on __context__ in Condition;Guido van Rossum2006-04-251-5/+1
| | | | | this can just call __context__ on the underlying lock. (The same change for Semaphore does *not* work!)
* Um, I thought I'd already checked this in.Guido van Rossum2006-03-101-6/+0
| | | | | | | Anyway, this is the changes to the with-statement so that __exit__ must return a true value in order for a pending exception to be ignored. The PEP (343) is already updated.
* Updates to the with-statement:Guido van Rossum2006-02-281-0/+29
| | | | | | | | | | | | | | | | - New semantics for __exit__() -- it must re-raise the exception if type is not None; the with-statement itself doesn't do this. (See the updated PEP for motivation.) - Added context managers to: - file - thread.LockType - threading.{Lock,RLock,Condition,Semaphore,BoundedSemaphore} - decimal.Context - Added contextlib.py, which defines @contextmanager, nested(), closing(). - Unit tests all around; bot no docs yet.
* Prevent threading.Thread.join() from blocking when a previous call raised anBrett Cannon2005-11-231-16/+18
| | | | | | exception (e.g., passing in an illegal argument). Applies patch #1314396. Thanks Eric Blossom.
* bug [ 1238170 ] threading.Thread uses {} as default argumentGeorg Brandl2005-07-151-1/+3
|
* Fixed typo in verbose output.Brett Cannon2005-01-271-1/+1
| | | | Closes bug #1110998. Thanks Matthew Bogosian.
* threading._DummyThread.__init__(): document obscure new code.Tim Peters2005-01-081-3/+9
| | | | | | | | test_threading.test_foreign_thread(): new test does a basic check that "foreign" threads can using the threading module, and that they create a _DummyThread instance in at least one use case. This isn't a very good test, since a thread created by thread.start_new_thread() isn't particularly "foreign".
* In _DummyThread objects the lock stored in __block (allocated thanks toBrett Cannon2005-01-081-0/+1
| | | | | | | | _Thread.__init__) was never used. This is a waste since locks use OS primitives that are in limited supply. So the lock is deleted in _DummyThread.__init__ . Closes bug #1089632.
generated by cgit v0.12 at 2024-12-25 07:38:12 (GMT)