-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
ENH: Non-nullable extension types #40554
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
Comments
Sounds like you want something like a database constraint but for DataFrames? That's an interesting idea, although I suspect this might be easiest to accomplish in end-user code by simply asserting that a given column contains no null values, rather than creating whole new data types. |
IMO nullability is part of the type definition, it's not some extra constraint to be tested by the end-user code. Checking the constraint in the extension code itself (e.g. in |
xref #40574 |
A 3rd party EA could just raise if any NA-like is passed to the relevant constructor or |
Looks like there's not much support for this feature from the core team so closing |
Uh oh!
There was an error while loading. Please reload this page.
As far as I can tell, all custom extension types are nullable. It would be useful to provide a way to create non-nullable extensions. One way to support this could be by setting the
na_value
attribute toNotImplemented
. Thoughts?The text was updated successfully, but these errors were encountered: