Message305198
I am not sure. This is a system bug and we often provide work-arounds
or even reimplementations of buggy time functions in the time and
datetime modules. Whether or not this is something that is worth
fixing is a question for the affected NetBSD users.
I would say, for the purposes of this issue - add a skip for NetBSD to
the failing test and add a test for another date that can be included
on all systems.
If motivated, please open a separate issue for the time.localtime() bug. |
|
Date |
User |
Action |
Args |
2017-10-29 23:25:06 | belopolsky | set | recipients:
+ belopolsky, serhiy.storchaka |
2017-10-29 23:25:06 | belopolsky | link | issue31894 messages |
2017-10-29 23:25:06 | belopolsky | create | |
|