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
However, this appears to be a new quirk of Pandas 0.24's CustomBusinessDay class and its use of pandas._libs.tslibs.conversion.localize_pydatetime(). Other offset functions don't seem to be affected, for the ones I've tried.
Everything worked just fine with Pandas 0.23.4 and earlier, with the latest freezegun-0.3.11.
Code Sample, a copy-pastable example if possible
Test setup: Python 2.7 and 3.6 on OS X using freezegun-0.3.11 with pandas-0.24.2
I originally opened an issue with Freezegun:
spulec/freezegun#284
However, this appears to be a new quirk of Pandas 0.24's
CustomBusinessDay
class and its use ofpandas._libs.tslibs.conversion.localize_pydatetime()
. Other offset functions don't seem to be affected, for the ones I've tried.Everything worked just fine with Pandas 0.23.4 and earlier, with the latest freezegun-0.3.11.
Code Sample, a copy-pastable example if possible
Test setup: Python 2.7 and 3.6 on OS X using freezegun-0.3.11 with pandas-0.24.2
Problem description
Failure mode:
Expected Output
All of these should work equally well, including
CustomBusinessDay
.Output of
pd.show_versions()
The text was updated successfully, but these errors were encountered: