You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
atombear opened this issue
May 16, 2025
· 1 comment
Labels
A-panicArea: code that results in panic exceptionsacceptedReady for implementationbugSomething isn't workingP-mediumPriority: mediumpythonRelated to Python Polars
Doing some initial investigation, this seems to be a regression from the recent fixes to .explode() + .over(). It is a mismatch between the type check result from .over and what is actually done in the engines. I need to have it a bit more clear what the signature of .over should be in this case.
A-panicArea: code that results in panic exceptionsacceptedReady for implementationbugSomething isn't workingP-mediumPriority: mediumpythonRelated to Python Polars
Checks
Reproducible example
on polars
1.29.0
Log output
Issue description
this worked in 1.20
Expected behavior
pl.col("x")
andpl.col("x").list.explode().over("idx", mapping_strategy="join")
should be equivalent in this case.Installed versions
i see this on linux as well
The text was updated successfully, but these errors were encountered: