-
Notifications
You must be signed in to change notification settings - Fork 24
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
fix: update LDF.collect() for polars==0.19.8 #24
Conversation
fix: switch to *args/**kwargs
35dee81
to
fe51a43
Compare
Thanks I also ran into the issue, I've merged this fix into my own develop branch of patito fork. There isn't much activity in this repo anymore it seems. |
We're working on a migration to pydantic v2, it's just difficult to squeeze in development time between our jobs. |
Wouldn't it then make sense to at least merge all the fixes, so the current release works as expected? |
We have a work-in-progress branch that we are migrating the pydantic work with, and it is extensive enough that we didn't want to risk having to do rebases while still doing that. I agree that the fixes here are valuable, but we decided to prioritize the pydantic migration first. |
Are all the current issues accounted for in the Pydantic v2 release or will the same issues persist? |
We will likely have fixed some issues, while others will persist. We will rebase the PRs on the pydantic-migrated-version and then go through the PRs one by one. |
If you need any help to port the fixes to the pydantic-migrated version, I am happy to help there. We use Patito quite extensively in our codebase |
This is now fixed in the main branch :) |
polars
removed **kwargs fromLazyFrame.collect()
in the 0.19.8 release. Since the signature forpatito
's childLDF.collect
does not match that ofpl.LazyFrame.collect
, thetest_dummy_data
suite fails after upgradingpolars
. This PR movescollect
to an*args, **kwargs
pattern for better backward/forward compatibility. Tests pass withpolars==0.19.8
andpolars==0.18.7
.