Message348437
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | shihai1991 |
|---|---|
| Recipients | asvetlov, ncoghlan, shihai1991, yselivanov |
| Date | 2019-07-25.13:24:50 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1564061090.56.0.687728681932.issue36692@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
It looks like setstrace function trigger this codeline: https://github.com/python/cpython/blob/master/Modules/_asynciomodule.c#L2618 Looks we can use set_exception_handler() to catch this error, but i am not sure it is worth catching this error through adding a extended exception hander. so, Nick, what's your thought? REF: https://github.com/python/cpython/blob/master/Lib/asyncio/base_events.py#L1627 |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-07-25 13:24:50 | shihai1991 | set | recipients: + shihai1991, ncoghlan, asvetlov, yselivanov |
| 2019-07-25 13:24:50 | shihai1991 | set | messageid: <1564061090.56.0.687728681932.issue36692@roundup.psfhosted.org> |
| 2019-07-25 13:24:50 | shihai1991 | link | issue36692 messages |
| 2019-07-25 13:24:50 | shihai1991 | create | |