DEPR: invalid-for-dtype fill_value in unstack #62289
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mroeschke
reviewed
Sep 8, 2025
| old_dtype = dtype | ||
| dtype, fill_value = maybe_promote(dtype, fill_value) | ||
| if old_dtype != dtype: | ||
| if old_dtype.kind not in "iub": |
There was a problem hiding this comment.
Curious why we only need to warn for these numeric types.
There was a problem hiding this comment.
for int/bool dtypes, we can introduce NaNs which entail upcasting. For all other dtypes we should be able to unstack without having to upcast. same idea as not warning on int/bool in PDEP6
mroeschke
approved these changes
Sep 8, 2025
|
Thanks @jbrockmendel |
37 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
doc/source/whatsnew/vX.X.X.rstfile if fixing a bug or adding a new feature.