RetroSearch Browse

Wed Jun 6 01:11:38 CEST 2012 · https://mail.python.org/pipermail/python-dev/2012-June/119959.html

Alexander Belopolsky wrote:
> The problem is again the DST ambiguity.  One day a year, datetime(y,
> m, d, 1, 30, tzinfo=Local) represents two different times and another
> day it represents no valid time.
> 
> The documentation example (fixed in issue 9063) addresses the
> ambiguity by defaulting to standard time, but it does this at a cost
> of having no way to spell "the other hour."

What would be so bad about giving datetime objects
a DST flag? Apps that don't care could ignore it and
get results no worse than the status quo.

-- 
Greg

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-June/119959.html below:

[Python-Dev] TZ-aware local time