Message269378
The interpreter is not crashing in your case, so this is a mostly-unrelated problem. (The part that is related is that it is triggered by module finalization.) As Berker said, please open a new issue, but be warned that it may get closed as a being addressed by the issue for rewriting the python startup sequence (pep 432 I think, which I think Nick has resurrected), since this is a systemic problem. On the other hand there might be a way to fix it in the datetime module if someone decides it is worth doing. |
|
Date |
User |
Action |
Args |
2016-06-27 13:41:20 | r.david.murray | set | recipients:
+ r.david.murray, amaury.forgeotdarc, ncoghlan, pitrou, ned.deily, Arfrever, palm.kevin, python-dev, berker.peksag, pconnell, theDarkBrainer, isoschiz, Denny Weinberg |
2016-06-27 13:41:20 | r.david.murray | set | messageid: <1467034880.44.0.290627836357.issue17408@psf.upfronthosting.co.za> |
2016-06-27 13:41:20 | r.david.murray | link | issue17408 messages |
2016-06-27 13:41:19 | r.david.murray | create | |
|