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
Leverage pytz-deprecation-shim to break our dependency on pytz but minimize user disruption. We've held off on this for a long time due to the risk of breaking end user code that's relying on the timezone objects that we return being specifically pytz timezone instances, but after spending hours today tracking down a bug that turned out to be caused by pytz using local solar mean time instead of the correct UTC offset for any timestamp before December 13th 1901, I think it's time to concede that leaving the pytz dependency in place is causing more problems than removing it will.
The text was updated successfully, but these errors were encountered:
Leverage pytz-deprecation-shim to break our dependency on pytz but minimize user disruption. We've held off on this for a long time due to the risk of breaking end user code that's relying on the timezone objects that we return being specifically
pytz
timezone instances, but after spending hours today tracking down a bug that turned out to be caused bypytz
using local solar mean time instead of the correct UTC offset for any timestamp before December 13th 1901, I think it's time to concede that leaving thepytz
dependency in place is causing more problems than removing it will.The text was updated successfully, but these errors were encountered: