| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
(GH-23828)
The issue being resolved is shown in the 3.10 docs (if you select docs for older versions you won't see a visual glitch).
The newer sphinx version that produces the 3.10 docs doesn't treat the backslash to escape things in some situations it previously did..
(cherry picked from commit dcc997cd28ab33ebac44182ee55533c1b37689f7)
Co-authored-by: Andre Delfino <adelfino@gmail.com>
|
|
|
|
|
|
|
|
|
| |
* Add a glossary entry for the term "callback"
* Link to it in loop.call_soon() and in the "Concurrency and Multithreading" section
Co-authored-by: Kyle Stanley <aeros167@gmail.com>
(cherry picked from commit a16d6970496cae5ecab5aaea2b416a4b77527cc2)
Co-authored-by: Roger Iyengar <ri@rogeriyengar.com>
|
|
|
|
|
|
|
|
|
|
|
| |
GH- [bpo-39128](https://bugs.python.org/issue39128): happy eyeballs description
GH- [3.9] 39128 - happy eyeballs description (GH-18624)
GH- [3.8] 39128 - happy eyeballs description (GH-18624)
https://bugs.python.org/issue39128
(cherry picked from commit 8af4712a16e4b7d1b60f1faec13cd7a88da95f6a)
Co-authored-by: idomic <michael.ido@gmail.com>
|
|
|
|
|
|
|
| |
(GH-18315)
(cherry picked from commit 5305cc9dbfe8a5a0ab666511f3ba7f026c8983f8)
Co-authored-by: idomic <michael.ido@gmail.com>
|
|
|
|
|
|
| |
Mention that the function implicitly creates new event loop only if called from the main thread.
(cherry picked from commit 2c49becc69c05934996a00b902e4a4f089b91954)
Co-authored-by: Andrew Svetlov <andrew.svetlov@gmail.com>
|
|
|
|
|
|
|
|
| |
(cherry picked from commit b0d4949f1fb04f83691e10a5453d1e10e4598bb9)
Co-authored-by: Jesús Cea <jcea@jcea.es>
Co-authored-by: Jesús Cea <jcea@jcea.es>
|
|
|
|
|
|
|
| |
(GH-17311) (#17529)
(cherry picked from commit ab513a38c98695f271e448fe2cb7c5e39eeaaaaf)
Co-authored-by: Kyle Stanley <aeros167@gmail.com>
|
|
|
|
|
| |
(cherry picked from commit f900064ac4b35226caad7502abc8a7e64f1c0e9d)
Co-authored-by: Kyle Stanley <aeros167@gmail.com>
|
|
|
|
|
| |
(#16485)
See https://bugs.python.org/issue38242 for more details
|
|
|
|
|
| |
(cherry picked from commit 6793cce155f8875b10efd746cb0b34cb72263af7)
Co-authored-by: Xtreak <tir.karthi@gmail.com>
|
|
|
|
|
|
| |
When the Windows default event loop changed, `asyncio-policy.rst` was updated but `asyncio-eventloop.rst` was missed.
(cherry picked from commit 9ffca670ed4df42eb256e7144619a9d3a830e7c0)
Co-authored-by: Ben Darnell <ben@bendarnell.com>
|
|
|
|
|
| |
(GH-13786)" (#13802)
This reverts commit 0f0a30f4da4b529e0f7df857b9f575b231b32758.
|
|
|
|
|
|
|
| |
Add BaseEventLoop.wait_executor_on_close attribute: true by default.
loop.close() now waits for the default executor to finish by default.
Set loop.wait_executor_on_close attribute to False to not wait for
the executor.
|
|
|
|
|
|
| |
Follow-up for #1067
https://bugs.python.org/issue29883
|
|
|
|
|
| |
loop.subprocess_exec (GH-13586)
https://bugs.python.org/issue36686
|
|
|
|
|
|
|
|
|
|
| |
Added two keyword arguments, `delay` and `interleave`, to
`BaseEventLoop.create_connection`. Happy eyeballs is activated if
`delay` is specified.
We now have documentation for the new arguments. `staggered_race()` is in its own module, but not exported to the main asyncio package.
https://bugs.python.org/issue33530
|
|
|
|
|
|
|
|
|
| |
Given example does not run, loop variable is missing.
Secondly, this is bad example how to handle shutdown signal, because it would cause `RuntimeError: Event loop stopped before Future completed.`
Perhaps it would be better to cancel all tasks instead of closing loop directly?
Did not create issue, because question is quite simple.
|
|
|
|
|
|
|
|
|
|
|
|
| |
# [bpo-36651](https://bugs.python.org/issue36651): Fixed Asyncio Event Loop documentation inconsistency
In the documentation for the call_later and the call_at methods there is a note which says that the delay cannot be longer than a day, but both methods have a note saying that this limitation was removed in Python 3.8
Here I fixed this issue by removing the pre-exising note and added a versionchanged.
To test my changes I have rebuilt the documentation with ```make html```. I did not have any errors and the effected page displayed correctly on a browser.
https://bugs.python.org/issue36651
|
|
|
|
|
|
|
|
|
|
|
| |
is not clear (GH-11987)
[bpo-36074](https://bugs.python.org/issue36074): It becomes clear on that the None is still return for server closed.
https://bugs.python.org/issue36074
|
| |
|
|
|
|
|
|
| |
Fixes `loop.add_writer` and `loop.add_signal_handler` method documentation to correctly reference the callback parameter from method signature.
https://bugs.python.org/issue35395
|
|
|
| |
Needs backport to 3.7. In 3.6 the description is correct.
|
|
|
|
|
|
| |
Replace "Availability: xxx" with ".. availability:: xxx" in the doc.
Original patch by Georg Brandl.
Co-Authored-By: Georg Brandl <georg@python.org>
|
|
|
|
|
|
|
|
|
|
| |
Since ProactorEventLoop is now the default in 3.8, remove examples
using it explicitly on Windows.
https://bugs.python.org/issue34687
|
| |
|
|
|
| |
Co-authored-by: Elvis Pranskevichus <elvis@magic.io>
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
* bpo-33649: Refresh Tasks and Futures pages
* Fixes
* Fix markup
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rewritten/updated sections:
* Event Loop APIs
* Transports & Protocols
* Streams
* Exceptions
* Policies
* Queues
* Subprocesses
* Platforms
|
|
|
| |
Co-authored-by: Antti Haapala <antti.haapala@anttipatterns.com>
|
| |
|
|
|
|
|
|
|
| |
(GH-8533)
Various asyncio internals expect that the default executor is a
`ThreadPoolExecutor`, so deprecate passing anything else to
`loop.set_default_executor()`.
|
|
|
| |
This is a fixup to 19a44f63c738388ef3c8515348b4ffc061dfd627
|
| |
|
|
|
|
|
|
|
| |
* Fix AttributeError (not all SSL exceptions have 'errno' attribute)
* Increase default handshake timeout from 10 to 60 seconds
* Make sure start_tls can be cancelled correctly
* Make sure any error in SSLProtocol gets propagated (instead of just being logged)
|
| |
|
|
|
|
|
| |
Most of the parameters were added in 3.4.4 (b9bf913ab32), but this
change was not documented
|
|
|
| |
* Also in docs
|
| |
|
| |
|
|
|
|
| |
I've run some tests on 3.7 asyncio and it appears that too many
things assume that run_in_executor returns a Future.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* bpo-32662: Implement Server.start_serving() and Server.serve_forever()
New methods:
* Server.start_serving(),
* Server.serve_forever(), and
* Server.is_serving().
Add 'start_serving' keyword parameter to loop.create_server() and
loop.create_unix_server().
|