-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG: Too aggressive typing in NDFrame.align #31788
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
BUG: Too aggressive typing in NDFrame.align #31788
Conversation
Is this in reference to annotations or to runtime type checking? |
It's type checking, but can spill over to the run time because an |
Do any of the other usage of |
There should`t be more; here I assumed that left and right should be treated alike, which was a wrong idea. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
too quick on approval...can you add test?
b6cc420
to
0a4e997
Compare
Ok, I've added a test. |
thanks can we open an issue about how to improve / fix _ensure_type to make things like this work? |
Co-authored-by: Terji Petersen <[email protected]>
The type checking was too aggressive.
right
has typeAny
, so the wrapping in_ensure_type
should not be done.