datetime seems to be broken WRT timezones (even when you add them)
On 2020-02-11, Chris Angelico <rosuav at gmail.com> wrote:
>> That's the key piece of info. This does appear to work, though still
>> not on python2. That, as you say, is my problem. But thankfully Jon
>> Ribbens has the save:
> Isn't it time to stop going to great effort to support Python 2?
That depends on what existing systems people need to support. The main
project I work on pre-dates the existence of Python's 'datetime'
module, let alone Python 3. It still generally uses 1 and 0 for True
and False because True and False didn't exist when we started.
This project will never move to Python 3. It was a happy and momentous
day, fairly recently, when we were able to move to Python 2.7 - albeit
we're basically stuck on Python 2.7.5 (plus random patches from RedHat
making it not-really-2.7.5).
So while it's been about 6 years since anyone should have been
starting any new projects using Python 2, there are plenty of
projects that are older than that and still need supporting,
and often it'd take some pretty huge unavoidable requirement
to motivate a port to Python 3.