-
Notifications
You must be signed in to change notification settings - Fork 16
Upgrade indicators to pandas v2.0.0 #1820
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
Comments
Are we sure #1825 was fully tested for pandas v2 compatibility? I discovered recently that we are still stuck with " |
|
FWIW, cmu-delphi/covidcast#618 (covidcast Pandas<2 pin PR) was merged after #1825, so at the very least, the latter was definitely tested on Pandas>2. Nat made all the tests pass and I did a number of passes through the changelog and searching the repo for changed functions, trying to be thorough. Side-note: it'd be nice if we had a way to easily AB test changes. Like, if we could deploy a Pandas>2 branch and compare its outputs with prod for a few weeks, we could increase our confidence in the change. |
Ah, good call. To fill the timeline out a little more: it looks like The lack of that pin does not necessarily guarantee we actually used pandas v2 in that time (the aforementioned #1994 wouldve been able to tell us that for sure) because some other package mightve affected the requirement constraints (for instance, Reclosing! |
Pandas v2.0.0 was released 2023-04-03, and includes a few breaking changes. Among them:
.sum()
now handles all types by default (e.g. strings, which get concatenated). There's a parameter to restrict to numeric types only..append()
not allowed for data frames.iteritems()
not allowed for seriesWe've pinned to <2.0 for now, but we should start working on fixing our code to work with v2.
The text was updated successfully, but these errors were encountered: