Python specific: - `pytz.timezone(timezone_name)` will give you the current offset for that timezone - well, it will at least be some consistent offset - surel

Python specific: - `pytz.timezone(timezone_name)` will give you the current offset for that timezone - well, it will at least be some consistent offset - surely, every timezone has the same reference starting point? What `pytz.timezone(name)` actually does is initialize a timezone object at the point in time of the first entry in the tz database for that zone. For example, New York had an offset of 4:56:02 prior to 1883 November 18, 12:03:58 [1]. That is the "starting point" for America/New_York and US/Eastern (which I think is an alias of New_York before a certain date). Which is why you get >>> pytz.timezone('America/New_York') <DstTzInfo 'America/New_York' LMT-1 day, 19:04:00 STD> Ish. Not sure where those 2 seconds went. But that explains why you see that strange 19:04 (-3:56) offset. The real way to use it is >>> pytz.timezone('America/New_York').localize(your_specific_datetime) Timezones without a reference time are deceptive. [1] https://en.wikipedia.org/wiki/Tz_database#Example_zone_and_rule_lines https://en.wikipedia.org/wiki/Tz_database#Example_zone_and_r...