datetime and timezone conversion with pytz - mind blowing behaviour
27,762
The documentation http://pytz.sourceforge.net/ states "Unfortunately using the tzinfo argument of the standard datetime constructors 'does not work' with pytz for many timezones." The code:
t = datetime(
2013, 5, 11, hour=11, minute=0,
tzinfo=pytz.timezone('Europe/Warsaw')
)
doesn't work according to this, instead you should use the localize method:
t = pytz.timezone('Europe/Warsaw').localize(
datetime(2013, 5, 11, hour=11, minute=0))
Author by
yakxxx
Geek with hacker mind-set, Python enthusiast, Linux user, Javascript coder, Network programmer, Machine learning hobbyst Follow me on twitter: @yakxxx88
Updated on October 30, 2020Comments
-
yakxxx over 3 years
I'm trying to convert timezone aware
datetime
object to UTC and then back to it's original timezone. I have a following snippett = datetime( 2013, 11, 22, hour=11, minute=0, tzinfo=pytz.timezone('Europe/Warsaw') )
now in ipython:
In [18]: t Out[18]: datetime.datetime( 2013, 11, 22, 11, 0, tzinfo=<DstTzInfo 'Europe/Warsaw' WMT+1:24:00 STD> )
and now let's try to do conversion to UTC and back. I would expect to have the same representation as:
In [19]: t.astimezone(pytz.utc).astimezone(pytz.timezone('Europe/Warsaw')) Out[19]: datetime.datetime( 2013, 11, 22, 10, 36, tzinfo=<DstTzInfo 'Europe/Warsaw' CET+1:00:00 STD> )
Yet we see that
Out[18]
andOut[19]
differ. What's going on?