-
Notifications
You must be signed in to change notification settings - Fork 173
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
Fdedup package versioning and windows fixes #1003
Conversation
Signed-off-by: Constantin Adam <[email protected]>
Signed-off-by: Constantin Adam <[email protected]>
@@ -1,9 +1,9 @@ | |||
pyyaml>=6.0.2 | |||
boto3>=1.34.69 | |||
kubernetes>=30.1.0 | |||
polars==1.9.0 | |||
polars>=1.13.0 |
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.
Please consider relaxing this to polars>=1.9.0. I have other modules that depend on polars and I want to make sure that all packages work together and meet the minimum requirements. Would your code break with 1.9.0 ?
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.
As I mentioned in issue #982, fuzzy dedup does not work with the following polars
releases:
- 1.10.0
- 1.11.0
- 1.12.0
It works with any release before, and including1.9.0
and after, or including 1.13.1. As long as you can exclude these three particular versions from polars, we are good.
Signed-off-by: Constantin Adam <[email protected]>
Signed-off-by: Constantin Adam <[email protected]>
Signed-off-by: Constantin Adam <[email protected]>
Signed-off-by: Maroun Touma <[email protected]>
Signed-off-by: Maroun Touma <[email protected]>
Why are these changes needed?
mmh3
andpolars
packagesRelated issue number (if any).
#982
#989