Every time I have to do this it takes me a solid half hour to figure it out, so I'm throwing it up here for future reference. I hate timezone calculations.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 | import pytz
import dateutil.parser
TZINFOS = {
'PDT': pytz.timezone('US/Pacific'),
# ... add more to handle other timezones
# (I wish pytz had a list of common abbreviations)
}
datestring = '11:45:00 Aug 13, 2008 PDT'
# Parse the string using dateutil
datetime_in_pdt = dateutil.parser.parse(datestring, tzinfos= TZINFOS)
# t is now a PDT datetime; convert it to UTC
datetime_in_utc = datetime_in_pdt.astimezone(pytz.utc)
# Let's convert it to a naive datetime object
datetime_naive = datetime_in_utc.replace(tzinfo = None)
|
More like this
- Template tag - list punctuation for a list of items by shapiromatron 11 months, 1 week ago
- JSONRequestMiddleware adds a .json() method to your HttpRequests by cdcarter 11 months, 2 weeks ago
- Serializer factory with Django Rest Framework by julio 1 year, 6 months ago
- Image compression before saving the new model / work with JPG, PNG by Schleidens 1 year, 7 months ago
- Help text hyperlinks by sa2812 1 year, 7 months ago
Comments
This is great, and I'd note that it suggests how to parse date strings that don't have timezone info, but for which the timezone is known. For example, if you access a service on the US east coast, and it is known to respond with datetime strings in local time, but without an explicit tz suffix, you can parse it with:
This does not rely at all on the local machine's timezone, so should work wherever it runs. I'd love to hear if there's an easier way.
#
Please login first before commenting.