-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Upgrade Dependency Ranges for 1.1 #4024
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
Conversation
|
1 similar comment
|
|
| "boto3": ">=1.10,<2", # <2 because unlikely to introduce breaking changes in minor releases. >=1.10 because 1.10 is 3 years old, no need to support older | ||
| "numpy": ">=1.21,<1.29", # "<{N+3}" upper cap, where N is the latest released minor version, assuming no warnings using N | ||
| "pandas": ">=2.0.0,<2.2.0", # "<{N+1}" upper cap | ||
| "pandas": ">=2.0.0,<2.3.0", # "<{N+1}" upper cap |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pandas 2.2 introduced a breaking change to how time frequency aliases are represented as strings (https://pandas.pydata.org/docs/whatsnew/v2.2.0.html#other-deprecations). For example, pandas.tseries.frequencies.to_offset("1min") returns
minin pandas >=2.2Tin pandas <2.2
I will need to change our logic for detecting seasonality to take this into account.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moving pandas upgrade to a separate PR to isolate the change
suzhoum
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
prateekdesai04
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.