bpo-36916: Swallow unhandled exception#13313
Conversation
|
When you're done making the requested changes, leave the comment: |
Sorry, something went wrong.
|
I have made the requested changes; please review again. Well, actually I did nothing but provide a comment that describes why ignoring the exception in this particular case is ok. |
Sorry, something went wrong.
|
Thanks for making the requested changes! @vstinner: please review the changes made to this pull request. |
Sorry, something went wrong.
|
Honestly, I don't understand how it can be a good idea to silently ignore errors. But this PR fix the warning on my Windows VM when running test_drain_raises() on Windows, so I approved it. My main concern right now is that https://bugs.python.org/issue36870 is breaking the Python CI and the Python workflow. |
Sorry, something went wrong.
|
Thanks, @vstinner |
Sorry, something went wrong.
|
@vstinner Please don't merge asyncio PRs without my review. This one looks fine though. |
Sorry, something went wrong.
test_asyncio was causing a lot of troubles, please see https://bugs.python.org/issue36870 for the context. @asvetlov: Can you please also fix Python 3.7? Python 3.7 is also affected by https://bugs.python.org/issue36870 |
Sorry, something went wrong.
|
By the way, it's not the first time that the Python CI and the Python workflow is broken by test_asyncio, especially by random failures on Windows. I'm not sure how to prevent these issues. The policy for the CI is to revert a change which introduces a regression: https://pythondev.readthedocs.io/ci.html#revert-on-fail That's what I did: PR #13316. But @asvetlov asked me to look at this PR instead. |
Sorry, something went wrong.
|
Sorry, @asvetlov and @vstinner, I could not cleanly backport this to |
Sorry, something went wrong.
The PR fixes a message about an unhandled exception in a task when
writer.write()is used without await butwriter.drain()fails with an exception.https://bugs.python.org/issue36916