-
Notifications
You must be signed in to change notification settings - Fork 3
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
add support for polars 1 #73
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #73 +/- ##
=======================================
Coverage 98.10% 98.10%
=======================================
Files 2 2
Lines 211 211
=======================================
Hits 207 207
Misses 4 4 ☔ View full report in Codecov by Sentry. |
@@ -9,7 +9,7 @@ platforms = ["linux-64", "osx-arm64", "osx-64", "win-64"] | |||
|
|||
[dependencies] | |||
python = ">=3.9" | |||
polars = ">=0.14.24,<0.21" | |||
polars = ">=0.14.24,<2" |
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.
I think we should pin to <1.1
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.
shouldn't the next breaking change be polars 2? since we are not touching polars internals but only the public api, this should be fine imo. but if you have strong opinions on this, we can also pin to <1.1
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.
They might add unsupported syntax without bumping the major version. Let's keep a rather tight pin to 1.1 or 1.2 here
No description provided.