summaryrefslogtreecommitdiffstats
path: root/Lib/threading.py
Commit message (Collapse)AuthorAgeFilesLines
* 00181-allow-arbitrary-timeout-in-condition-wait.patchFedora Python maintainers2020-09-291-7/+10
| | | | | | | | | | 00181 # Allow arbitrary timeout for Condition.wait, as reported in https://bugzilla.redhat.com/show_bug.cgi?id=917709 Upstream doesn't want this: http://bugs.python.org/issue17748 But we have no better solution downstream yet, and since there is no API breakage, we apply this patch. Doesn't apply to Python 3, where this is fixed otherwise and works.
* Improve threading.daemon docstring (GH-14278)Miss Islington (bot)2019-06-231-2/+1
| | | | | | Rephrase and clarify that "the entire Python program exits when only daemon threads are left". This matches the documentation at https://docs.python.org/3/library/threading.htmlGH-thread-objects. (cherry picked from commit bb110cc2ed81447fb48805f31146cf31323a8fc3) Co-authored-by: mbarkhau <mbarkhau@gmail.com>
* use the with statement for locking the internal condition (closes #25362)Benjamin Peterson2015-10-111-12/+3
| | | | Patch by Nir Soffer.
* reinitialize an Event's Condition with a regular lock (closes #25319)Benjamin Peterson2015-10-061-1/+1
|
* #11866: Eliminate race condition in the computation of names for new threads.R David Murray2014-10-041-4/+4
| | | | Original patch by Peter Saveliev.
* Issue #22423: Unhandled exception in thread no longer causes unhandledSerhiy Storchaka2014-09-211-4/+4
| | | | AttributeError when sys.stderr is None.
* LOL - 2.7 requires very different code. Annoying ;-)Tim Peters2013-10-091-4/+4
|
* Issue 19158: a rare race in BoundedSemaphore could allow .release() too often.Tim Peters2013-10-091-3/+5
| | | | (grafted from e06edc0c7a4951327f0c95ebeebccba6879a6063)
* Issue #18418: After fork(), reinit all threads states, not only active ones.Charles-François Natali2013-08-301-1/+1
| | | | Patch by A. Jesse Jiryu Davis.
* Issue #11714: Use 'with' statements to assure a Semaphore releases aSerhiy Storchaka2013-04-221-22/+20
| | | | condition variable. Original patch by Thomas Rachel.
* Issue #17375: Add docstrings to the threading module.Raymond Hettinger2013-03-091-5/+346
|
* Fix #15567. collections.deque wasn't importedBrian Curtin2012-08-101-1/+2
|
* Issue #14308: Fix an exception when a "dummy" thread is in the threading ↵Antoine Pitrou2012-04-191-0/+4
| | | | module's active list after a fork().
* remove unused importBenjamin Peterson2012-02-041-1/+0
|
* Issue #11870: threading: Properly reinitialize threads internal locks andCharles-François Natali2011-12-181-8/+5
| | | | condition variables to avoid deadlocks in child processes.
* backport fix from r87741 related to the issue6643 fix in r87727.Gregory P. Smith2011-01-041-2/+4
|
* Merged revisions 87710 via svnmerge fromGregory P. Smith2011-01-041-0/+18
| | | | | | | | | | | | | | | | | svn+ssh://pythondev@svn.python.org/python/branches/py3k ........ r87710 | gregory.p.smith | 2011-01-03 13:06:12 -0800 (Mon, 03 Jan 2011) | 4 lines issue6643 - Two locks held within the threading module on each thread instance needed to be reinitialized after fork(). Adds tests to confirm that they are and that a potential deadlock and crasher bug are fixed (platform dependant). ........ This required a bit more fiddling for 2.x as __block and __started are __ private as well as the __started Event's __cond. A new "private" _reset_internal_locks() method is added to Thread and _Event objects to address this.
* Merged revisions 87341 via svnmerge fromAntoine Pitrou2010-12-171-2/+8
| | | | | | | | | | | svn+ssh://pythondev@svn.python.org/python/branches/py3k ........ r87341 | antoine.pitrou | 2010-12-17 18:42:16 +0100 (ven., 17 déc. 2010) | 4 lines Issue #4188: Avoid creating dummy thread objects when logging operations from the threading module (with the internal verbose flag activated). ........
* 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
|
generated by cgit v0.12 at 2025-08-28 03:41:51 (GMT)