-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error with latest version of Pandas #40
Comments
The issue seems to have been introduced with the latest version of Pandas (1.3.0). After downgrading to the previous version (1.2.5), it no longer occurs. |
With the upgrade to Numpy 1.21.0 and Pandas 1.3.0 I've experienced "TypeError: int() argument must be a string, a bytes-like object or a number, not 'NaTType'" The offending line of code is line 6 in calendar_helpers: NP_NAT = np.array([pd.NaT], dtype=np.int64)[0] I've changed my local copy to : NP_NAT = np.array([pd.NaT.asm8.view('i8')], dtype=np.int64)[0] Recompiled and it seems to work fine. |
Another issue following this latest pandas release is that the ExchangeCalendar constructor is now raising a FutureWarning. The cause is within the creation of the schedule
One option would be to change the target dtype to "datetime64[ns, UTC]" thereby defining the schedule columns in terms of UTC. This additional context would be meaningful although I suspect it would open a can of worms with respect to changes it would necessitate within |
* Fix #40 * Fix ExchangeCalendar.__init__ pandas FutureWarning
I recently updated my packages, and now when calling
from exchange_calendars import get_calendar
, I get the following error:This occurs both on macOS with Python 3.7 and Ubuntu with Python 3.8.
The text was updated successfully, but these errors were encountered: