4 Commits

Author	SHA1	Message	Date
Miss Islington (bot)	12073fc6fd	Trivial typo in docstring (#27504) ... (cherry picked from commit 4b4227b907) Co-authored-by: Jesús Cea <jcea@jcea.es> Co-authored-by: Jesús Cea <jcea@jcea.es>	2021-07-31 07:04:45 +02:00
Kyle Stanley	2b201369b4	Fix asyncio.to_thread() documented return type (GH-20547) ... When I wrote the documentation for `asyncio.to_thread()`, I mistakenly assumed that `return await loop.run_in_executor(...)` within an async def function would return a Future. In reality, it returns a coroutine. This likely won't affect typical usage of `asyncio.to_thread()`, but it's important for the documentation to be correct here. In general, we also tend to avoid returning futures from high-level APIs in asyncio.	2020-05-31 00:07:04 -07:00
Kyle Stanley	0f56263e62	bpo-32309: Add support for contextvars in asyncio.to_thread() (GH-20278) ... Allows contextvars from the main thread to be accessed in the separate thread used in `asyncio.to_thread()`. See the [discussion](https://github.com/python/cpython/pull/20143#discussion_r427808225) in GH-20143 for context. Automerge-Triggered-By: @aeros	2020-05-20 22:20:43 -07:00
Kyle Stanley	cc2bbc2227	bpo-32309: Implement asyncio.to_thread() (GH-20143) ... Implements `asyncio.to_thread`, a coroutine for asynchronously running IO-bound functions in a separate thread without blocking the event loop. See the discussion starting from [here](https://github.com/python/cpython/pull/18410#issuecomment-628930973) in GH-18410 for context. Automerge-Triggered-By: @aeros	2020-05-18 20:03:28 -07:00