-
-
Notifications
You must be signed in to change notification settings - Fork 10.9k
ENH: Implement concatenate dtype and casting keyword arguments #16134
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
Conversation
369cac8
to
ab101e8
Compare
596f057
to
f8755f9
Compare
OK, last commit should have fixed the test failure (potential use-after free of |
@seberg there is a merge conflict |
f6b6d34
to
266b4af
Compare
Hmmm, not sure why the code-cov is so bad, I am not quite certain whether or not it considers the Deprecation warning tested, but I guess the problem is just the C-API code... I found another small bug thinking about adding a few more tests for untested Errors :)... |
yep looks bad. I guess its able to correctly flag the coverage thing, but not able to point exactly what the issue is. |
Unfortunately, the casting was not consistent and sometimes used force casting (axis=None) while normally same kind casting was used. This thus deprecates the `force_casting` corner case, so that casting has to be provided in the future.
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
266b4af
to
3c746b0
Compare
s390x is failing typing tests, with |
Co-authored-by: Matti Picus <matti.picus@gmail.com>
Thanks @seberg |
Unfortunately, the casting was not consistent and sometimes used
force casting (axis=None) while normally same kind casting was used.
This thus deprecates the
force_casting
corner case, so thatcasting has to be provided in the future.
Builds on top of gh-16133 (so marking it draft) and is partially motivated as by making gh-15925 an easier transition.
The deprecation should be pretty rare, since it is in the
axis=None
corner-case only.