Message314241
Seems it was fixed somewhere between 3.6.3 and 3.6.5+.
Traceback (most recent call last):
File "baderror.py", line 10, in <module>
raise e from e
__main__.BadError
3.5 is now in security-only fixes stage, and this doesn't look like a security issue. |
|
Date |
User |
Action |
Args |
2018-03-22 09:58:00 | serhiy.storchaka | set | recipients:
+ serhiy.storchaka, xcombelle, josh.r, JelleZijlstra |
2018-03-22 09:58:00 | serhiy.storchaka | set | messageid: <1521712680.13.0.467229070634.issue28962@psf.upfronthosting.co.za> |
2018-03-22 09:58:00 | serhiy.storchaka | link | issue28962 messages |
2018-03-22 09:58:00 | serhiy.storchaka | create | |
|