-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
BUG: need better inference for path in Series construction (GH9456) #9924
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
Closed
Closed
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
f883b79
TST: Adding test for bug GH 9456
patrickfournier a934792
BUG: GH 9456 Fixed Series.__init__ to better handle dict data
patrickfournier 04eeabe
Merge branch 'master' into issue-9456
patrickfournier c59c4fe
BUG: GH 9456 Fixed Series.__init__ to better handle dict data
patrickfournier File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
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.
see why this path is hit in the first place and can go from there.
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.
Before I added
.value
at line 171,lib.fast_multiget
was throwing aTypeError
. Now, theelse
clause must handles the conversion of datetime64 dicts because we cannot compare aTimestamp
with adatetime64
: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.
that's not what I mean. put halt in there and see what test actually hits this. This is handling an edge case. Your fix, just confuses things. I think there is a more general soln.
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.
I ran the tests and reported the results in the issue: #9456.
Maybe a better fix would be to correctly handle the comparison between Timestamp and datetime64?
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.
The idea is to have the least special cases as possible. You rarely actually want to convert a
DatetimeIndex
using.astype('O')
this is the least desirable result (though it may have been done for some reason). But it is tricky because a user can passTimestamp/datetime.datetime/datetime.date/np.datetime64
as elements and a non-index like (but that is index-like). Best best is to do_ensure_index
which will convert list-like things to anIndex
(and possibly to aDatetimeIndex
if its compat; if its not then all bets are off).