Fix: interval_range infers incorrect integer dtype for np.float32 input #63052
+15
−4
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
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
interval_rangeignores type ofstart(regression from pandas 2.2.2) #58964doc/source/whatsnew/vX.X.X.rstfile if fixing a bug or adding a new feature.This PR fixes a bug where
pd.interval_rangewould incorrectly infer an integerdtypewhen one of the inputs (e.g.,start) was anp.float32and other inputs (e.g.,end,freq) were integers. This resulted in a loss of precision.New Output