If you know your origin timezone and the new timezone that you want to convert it to, it turns out to be very straightforward: Make two pytz.timezone objects, one for the current timezone and one for the new timezone e.g. pytz.timezone(“US/Pacific”). You can find a list of all official timezones in pytz library: import pytz; … Read more
See: http://bytes.com/topic/python/answers/676275-pytz-giving-incorrect-offset-timezone In the comments, someone proposes to use tzinfo.localize() instead of the datetime constructor, which does the trick. >>> tz = timezone(‘Asia/Kolkata’) >>> dt = tz.localize(datetime.datetime(2011, 6, 20, 0, 0, 0, 0)) >>> dt datetime.datetime(2011, 6, 20, 0, 0, tzinfo=<DstTzInfo ‘Asia/Kolkata’ IST+5:30:00 STD>) UPDATE: Actually, the official pytz website states that you should always … Read more
For pytz timezones, use their .localize() method to turn a naive datetime object into one with a timezone: start_date = local_tz.localize(start_date) For timezones without a DST transition, the .replace() method to attach a timezone to a naive datetime object should normally also work: start_date = start_date.replace(tzinfo=local_tz) See the localized times and date arithmetic of the … Read more
This error occurs when installing pytz using pip v1.4 or newer, due to this change in behaviour: Pre-release Versions Starting with v1.4, pip will only install stable versions as specified by PEP426 by default. If a version cannot be parsed as a compliant PEP426 version then it is assumed to be a pre-release. If a … Read more
Time zones and offsets change over the years. The default zone name and offset delivered when pytz creates a timezone object are the earliest ones available for that zone, and sometimes they can seem kind of strange. When you use localize to attach the zone to a date, the proper zone name and offset are … Read more
Use tz.localize(d) to localize the instance. From the documentation: The first is to use the localize() method provided by the pytz library. This is used to localize a naive datetime (datetime with no timezone information): >>> loc_dt = eastern.localize(datetime(2002, 10, 27, 6, 0, 0)) >>> print(loc_dt.strftime(fmt)) 2002-10-27 06:00:00 EST-0500 If you don’t use tz.localize(), but … Read more
I think I got it: pytz.utc.localize(utc_time, is_dst=None).astimezone(tz) This line first converts the naive (time zone unaware) utc_time datetime object to a datetime object that contains a timezone (UTC). Then it uses the astimezone function to adjust the time according to the requested time zone.
Answer based on the answer by Carl Meyer in Google Groups Answer The reason for this difference, is that this is NOT the right way of converting a timezone agnostic datetime object to a timezone aware object. The explanation being: “A pytz timezone class does not represent a single offset from UTC, it represents a … Read more
localize just assumes that the naive datetime you pass it is “right” (except for not knowing about the timezone!) and so just sets the timezone, no other adjustments. You can (and it’s advisable…) internally work in UTC (rather than with naive datetimes) and use replace when you need to perform I/O of datetimes in a … Read more
To get a naive datetime object that represents time in UTC from “seconds since the epoch” timestamp: from datetime import datetime utc_dt = datetime.utcfromtimestamp(ts) If you want to get an aware datetime object for UTC timezone: import pytz aware_utc_dt = utc_dt.replace(tzinfo=pytz.utc) To convert it to some other timezone: tz = pytz.timezone(‘America/Montreal’) dt = aware_utc_dt.astimezone(tz) To … Read more