You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because these don't have a name, we can't set the TZ environment variable with the name straight from tzname or zone (see #58 for some context on that difference).
I'd suggest that a good solution might be to use the same behaviour as already exists here
It may be necessary to support both the tz_offset argument and the offset in the datetime_spec.tzinfo in the case that it's a datetime. It may also be necessary to combine these, but I'm not quite sure what the desired behaviour is when both a tz_offset and a timezone-aware datetime are provided.
The text was updated successfully, but these errors were encountered:
It's possible for a
tzinfo
object to only have an offset and no named timezone. For example:Because these don't have a name, we can't set the
TZ
environment variable with the name straight fromtzname
orzone
(see #58 for some context on that difference).I'd suggest that a good solution might be to use the same behaviour as already exists here
It may be necessary to support both the
tz_offset
argument and the offset in thedatetime_spec.tzinfo
in the case that it's adatetime
. It may also be necessary to combine these, but I'm not quite sure what the desired behaviour is when both atz_offset
and a timezone-awaredatetime
are provided.The text was updated successfully, but these errors were encountered: