-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
Series of unsigned dtype can't have diff() without upcast #4899
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
Labels
Bug
Dtype Conversions
Unexpected or buggy dtype conversions
Numeric Operations
Arithmetic, Comparison, and Logical operations
Comments
yep....can be fixed
|
The problem with upcasting is what you do with something like this:
|
yep...that should really be object even before the diff.... |
was this fixed? |
No, it's still open. |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Bug
Dtype Conversions
Unexpected or buggy dtype conversions
Numeric Operations
Arithmetic, Comparison, and Logical operations
This is not a Pandas issue but a numpy one.
see also #5230
However, it is highly confusing and it could be appropriate to fix in Pandas by promoting
uint(2^x) dtypes to int(2^(x+1))
inSeries.diff()
.The text was updated successfully, but these errors were encountered: