refactor(python)!: Remove re-export of type aliases #17032
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
PolarsDataType
at the top-leveldatatypes
module:OneOrMoreDataTypes
PolarsDataType
PolarsTemporalType
PythonDataType
SchemaDefinition
SchemaDict
We do not want to re-export type aliases for a few reasons:
I want to set up a proper
polars.typing
module like NumPy has, with a few 'blessed' type aliases. Until then, users are encouraged to define their own type aliases, or use thepolars.type_aliases
module though this module is not intended to be public and may be changed at any point.This is technically not breaking because we do not document the type aliases in the API reference, but all the same, there will probably be some people who were using these re-exports. So now with the 1.0.0 release it's a good opportunity to make this change.
Example
Before:
After: