Chris Jerdonek added the comment:
Regarding the documentation, I'm not sure we _need_ to say what happens in this
edge case for 3.9. It was already unspecified before 3.9, so we're not any
worse off. (The change in issue 40607 was, however, documented.)
I'd rather come to agreement on (1)
Yury Selivanov added the comment:
> 2) Add some warning about the value is thrown away (in debug mode) and
> document it somewhere.
The documentation update is definitely something that needs to be done in 3.9.
Want to submit a PR?
We can also issue a warning in asyncio debug mode.
I'm
New submission from Roman Skurikhin :
In https://bugs.python.org/issue40607 asyncio.wait_for behavior was changed so
it propagates exceptions that happened during cancellation. But it still raises
`TimeoutError` if cancelation ends with some value being returned. In the
following example
