Message291230
In the OP, the error is caused by `open` being unavailable, which is a builtin. According to what Serhiy says, this error would be after step 6 in his list, so `sys` wouldn't be available either, and nor perhaps would any other builtins.
As some termination issues are asyncio-related (e.g. this one, "coroutine was never awaited"), it would make more sense for this kind of error handling to happen there - there's more contextual information available than there is in logging, so the error message displayed would be more useful because it could use the additional context available. |
|
Date |
User |
Action |
Args |
2017-04-06 15:09:10 | vinay.sajip | set | recipients:
+ vinay.sajip, vstinner, smurfix, r.david.murray, methane, serhiy.storchaka, yselivanov, JanVok, Charles Bouchard-Légaré |
2017-04-06 15:09:10 | vinay.sajip | set | messageid: <1491491350.22.0.577539935465.issue26789@psf.upfronthosting.co.za> |
2017-04-06 15:09:10 | vinay.sajip | link | issue26789 messages |
2017-04-06 15:09:09 | vinay.sajip | create | |
|