summaryrefslogtreecommitdiffstats
path: root/Lib/asyncio/futures.py
Commit message (Collapse)AuthorAgeFilesLines
* gh-93453: No longer create an event loop in get_event_loop() (#98440)Serhiy Storchaka2022-12-061-2/+2
| | | | | | | | | | | | | | | asyncio.get_event_loop() now always return either running event loop or the result of get_event_loop_policy().get_event_loop() call. The latter should now raise an RuntimeError if no current event loop was set instead of creating and setting a new event loop. It affects also a number of asyncio functions and constructors which call get_event_loop() implicitly: ensure_future(), shield(), gather(), etc. DeprecationWarning is no longer emitted if there is no running event loop but the current event loop was set. Co-authored-by: Łukasz Langa <lukasz@langa.pl>
* GH-90985: Revert "Deprecate passing a message into cancel()" (#97999)Guido van Rossum2022-10-071-6/+0
| | | | | Reason: we were too hasty in deprecating this. We shouldn't deprecate it before we have a replacement.
* GH-96827: Don't touch closed loops from executor threads (#96837)Guido van Rossum2022-09-301-0/+2
| | | | | * When chaining futures, skip callback if loop closed. * When shutting down an executor, don't wake a closed loop.
* bpo-45924: Fix asyncio incorrect traceback when future's exception is raised ↵Kumar Aditya2022-07-111-1/+2
| | | | multiple times (GH-30274)
* bpo-46829: Deprecate passing a message into Future.cancel() and ↵Andrew Svetlov2022-03-231-0/+6
| | | | | Task.cancel() (GH-31840) After a long deliberation we ended up feeling that the message argument for Future.cancel(), added in 3.9, was a bad idea, so we're deprecating it in 3.11 and plan to remove it in 3.13.
* bpo-47039: Normalize repr() of asyncio future and task objects (GH-31950)Andrew Svetlov2022-03-171-4/+1
|
* bpo-45390: Propagate CancelledError's message from cancelled task to its ↵Andrew Svetlov2022-02-211-0/+5
| | | | | | awaiter (GH-31383) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
* bpo-46469: Make asyncio generic classes return GenericAlias (GH-30777)Kumar Aditya2022-01-221-2/+2
| | | | | | | | | | | | * bpo-46469: Make asyncio generic classes return GenericAlias * 📜🤖 Added by blurb_it. * Update Misc/NEWS.d/next/Library/2022-01-22-05-05-08.bpo-46469.plUab5.rst Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com> Co-authored-by: blurb-it[bot] <43283697+blurb-it[bot]@users.noreply.github.com> Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
* bpo-39529: Deprecate creating new event loop in asyncio.get_event_loop() ↵Serhiy Storchaka2021-04-251-2/+2
| | | | | | (GH-23554) asyncio.get_event_loop() emits now a deprecation warning when it creates a new event loop. In future releases it will became an alias of asyncio.get_running_loop().
* bpo-41241: Unnecessary Type casting in 'if condition' (GH-21396)Wansoo Kim2020-11-281-1/+1
| | | | | | | | This is my first issue! So, if there's anything wrong, please tell me! Also, thank you always for all the contributors! Automerge-Triggered-By: GH:asvetlov
* bpo-31033: Improve the traceback for cancelled asyncio tasks (GH-19951)Chris Jerdonek2020-05-181-5/+21
| | | | | When an asyncio.Task is cancelled, the exception traceback now starts with where the task was first interrupted. Previously, the traceback only had "depth one."
* bpo-31033: Add a msg argument to Future.cancel() and Task.cancel() (GH-19979)Chris Jerdonek2020-05-151-3/+8
|
* bpo-38978: Implement __class_getitem__ for asyncio objects (GH-17491)Batuhan Taşkaya2019-12-071-0/+3
| | | https://bugs.python.org/issue38978
* bpo-38785: Prevent asyncio from crashing (GH-17144)Andrew Svetlov2019-11-131-1/+4
| | | | | | | if parent `__init__` is not called from a constructor of object derived from `asyncio.Future` https://bugs.python.org/issue38785
* bpo-34622: Extract asyncio exceptions into a separate module (GH-9141)Andrew Svetlov2018-09-111-12/+21
|
* bpo-33469: RuntimeError after closing loop that used run_in_executor (GH-7171)Yury Selivanov2018-05-281-0/+3
|
* bpo-32643: Drop support for a few private Task and Future APIs. (#5293)Yury Selivanov2018-01-241-4/+4
| | | | | | | | Specifically, it's not possible to subclass Task/Future classes and override the following methods: * Future._schedule_callbacks * Task._step * Task._wakeup
* bpo-32436: Implement PEP 567 (#5027)Yury Selivanov2018-01-231-6/+11
|
* bpo-31721: Allow Future._log_traceback to only be set to False (#5009)Yury Selivanov2017-12-251-6/+16
|
* bpo-32363: Disable Task.set_exception() and Task.set_result() (#4923)Yury Selivanov2017-12-251-3/+4
|
* bpo-32415: Add asyncio.Task.get_loop() and Future.get_loop() (#4992)Yury Selivanov2017-12-231-2/+18
|
* bpo-32311: Implement asyncio.create_task() shortcut (#4848)Andrew Svetlov2017-12-151-1/+3
| | | | | * Implement functionality * Add documentation
* bpo-32258: Replace 'yield from' to 'await' in asyncio docs (#4779)Andrew Svetlov2017-12-111-2/+3
| | | | | | * Replace 'yield from' to 'await' in asyncio docs * Fix docstrings
* bpo-32262: Fix codestyle; use f-strings formatting where necessary. (#4775)Yury Selivanov2017-12-101-8/+10
|
* asyncio: Remove asyncio/compat.py (#4606)Victor Stinner2017-11-281-3/+1
| | | | | | | | | | The asyncio/compat.py file was written to support Python < 3.5 and Python < 3.5.2. But Python 3.5 doesn't accept bugfixes anymore, only security fixes. There is no more need to backport bugfixes to Python 3.5, and so no need to have a single code base for Python 3.5, 3.6 and 3.7. Say hello (again) to "async" and "await", who became real keywords in Python 3.7 ;-)
* asyncio: Remove unused Future._tb_logger attribute (#4596)Victor Stinner2017-11-271-8/+1
| | | | It was only used on Python 3.3, now only Future._log_traceback is used.
* bpo-31970: Reduce performance overhead of asyncio debug mode. (#4314)Antoine Pitrou2017-11-071-1/+1
| | | | * bpo-31970: Reduce performance overhead of asyncio debug mode.
* bpo-31960: Fix asyncio.Future documentation for thread (un)safety. (#4319)Antoine Pitrou2017-11-071-1/+3
|
* bpo-30508: Don't log exceptions if Task/Future "cancel()" method called (#2050)Yury Selivanov2017-06-111-0/+1
|
* bpo-29617: Remove Python 3.3 support from asyncio (GH-232)INADA Naoki2017-04-251-106/+16
|
* Issue #28544: Implement asyncio.Task in C.Yury Selivanov2016-10-281-71/+18
| | | | | | | | This implementation provides additional 10-20% speed boost for asyncio programs. The patch also fixes _asynciomodule.c to use Arguments Clinic, and makes '_schedule_callbacks' an overridable method (as it was in 3.5).
* asyncio: Increase asyncio.Future test coverage; test both implementations.Yury Selivanov2016-10-241-2/+7
| | | | | Also, add 'isfuture' to 'asyncio.futures.__all__', so that it's exposed as 'asyncio.isfuture'.
* Issue #28448: Fix C implemented asyncio.Future didn't work on WindowsINADA Naoki2016-10-211-4/+4
|
* Issue #28452: Remove _asyncio._init_module functionINADA Naoki2016-10-181-15/+8
|
* Issue #28428: Rename _futures module to _asyncio.INADA Naoki2016-10-151-3/+3
| | | | It will have more speedup functions or classes other than asyncio.Future.
* Issue #26801: Added C implementation of asyncio.Future.INADA Naoki2016-10-091-37/+57
| | | | Original patch by Yury Selivanov.
* Merge asyncio upstream.Guido van Rossum2016-09-091-6/+18
|
* Rename Future._blocking to _asyncio_future_blocking.Guido van Rossum2016-09-091-2/+10
| | | | | | | | | | | | This is now an official "protected" API that can be used to write classes that are duck-type-compatible with Future without subclassing it. (For that purpose I also changed isinstance(result, Future) to check for this attribute instead.) Hopefully Amber Brown can use this to make Twisted.Deferred compatible with asyncio.Future. Tests and docs are TBD.
* Issue #27041: asyncio: Add loop.create_future methodYury Selivanov2016-05-161-1/+3
|
* asyncio: Prevent StopIteration from being thrown into a FutureYury Selivanov2016-03-021-0/+3
| | | | Patch by Chris Angelico (issue #26221)
* Issue #26304: Change "allows to <verb>" to "allows <verb>ing" or similarMartin Panter2016-02-101-1/+1
| | | | | The original form is incorrect grammar and feels awkward, even though the meaning is clear.
* asyncio: Cleanup Future APIYury Selivanov2015-11-171-30/+30
| | | | See https://github.com/python/asyncio/pull/292 for details.
* Issue #25304: Add asyncio.run_coroutine_threadsafe(). By Vincent Michel.Guido van Rossum2015-10-031-16/+58
|
* asyncio: Add asyncio.compat moduleVictor Stinner2015-07-251-6/+4
| | | | | Move compatibility helpers for the different Python versions to a new asyncio.compat module.
* asyncio: Support PEP 492. Issue #24017.Yury Selivanov2015-05-121-0/+4
|
* Asyncio issue 222 / PR 231 (Victor Stinner) -- fix @coroutine functions ↵Guido van Rossum2015-05-031-1/+1
| | | | without __name__.
* Issue #23243, asyncio: Emit a ResourceWarning when an event loop or a transportVictor Stinner2015-01-291-3/+3
| | | | is not explicitly closed. Close also explicitly transports in test_sslproto.
* Issue #23209: Break some reference cycles in asyncio. Patch written by MartinVictor Stinner2015-01-091-1/+1
| | | | Richard.
* asyncio: sync with TulipVictor Stinner2015-01-091-2/+0
| | | | | | | * Tulip issue 184: FlowControlMixin constructor now get the event loop if the loop parameter is not set. Add unit tests to ensure that constructor of StreamReader and StreamReaderProtocol classes get the event loop. * Remove outdated TODO/XXX
* asyncio: Initialize more Future and Task attributes in the class definition toVictor Stinner2014-12-041-2/+1
| | | | avoid attribute errors in destructors.
generated by cgit v0.12 at 2025-04-18 04:27:31 (GMT)