clip()
with lower bound > upper bound panicks, but only in dev profile
#19692
Labels
bug
Something isn't working
needs triage
Awaiting prioritization by a maintainer
python
Related to Python Polars
Uh oh!
There was an error while loading. Please reload this page.
Checks
Reproducible example
Log output
Issue description
I'm not sure whether this is a bug or not but depending on the build profile,
clip()
either works or panicks whenlower_bound > upper_bound
:dev
profile (aftermake build
), using for instance.clip(lower_bound=10, upper_bound=0)
panicks with the message displayed abovepolars
withpip
), it returns this:My issue here is that I contribute to
r-polars
and when I want to test this behavior (in dev profile) I get a panick instead of a proper error. This issue disappears once I compile the package with release profile but then I can't run tests anymore. Therefore, I'd like to know if this is expected.Expected behavior
Unsure, I'd say the behavior should be the same in dev and release profiles (but should it error or return 10 as in the release profile?).
Installed versions
The text was updated successfully, but these errors were encountered: