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
Describe the bug
The nullability constraint is not enforced in pl.DataFrame when the underlying data type is pl.Float64. When I provide a pl.DataFrame with a float column that contains None, it passes.
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pandera.
The validation should vail as the column col contains a None value, but the schema requires it to be non-nullable.
Desktop (please complete the following information):
OS: MacOS
Browser: Chrome
Additional context
The nullability constraint is correctly enforced if the underlying data type is int or str.
For float, the nullability constraint correctly detects NULL values in the form of np.nan.
The text was updated successfully, but these errors were encountered:
Describe the bug
The nullability constraint is not enforced in
pl.DataFrame
when the underlying data type ispl.Float64
. When I provide apl.DataFrame
with a float column that containsNone
, it passes.Code Sample, a copy-pastable example
Expected behavior
The validation should vail as the column
col
contains aNone
value, but the schema requires it to be non-nullable.Desktop (please complete the following information):
Additional context
The nullability constraint is correctly enforced if the underlying data type is
int
orstr
.For
float
, the nullability constraint correctly detects NULL values in the form ofnp.nan
.The text was updated successfully, but these errors were encountered: