Skip to content

REF: standardize reso-return in parsing #50914

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 6 commits into from
Jan 25, 2023
Merged

REF: standardize reso-return in parsing #50914

merged 6 commits into from
Jan 25, 2023

Conversation

jbrockmendel
Copy link
Member

Moving towards getting reso inference working in the remaining cases in convert_string_to_tsobject, and hopefully de-duplicating parse_datetime_string vs parse_datetime_string_with_reso

@mroeschke mroeschke added Refactor Internal refactoring of code Non-Nano datetime64/timedelta64 with non-nanosecond resolution labels Jan 23, 2023
@jbrockmendel jbrockmendel mentioned this pull request Jan 25, 2023
Merged
@jbrockmendel
Copy link
Member Author

@mroeschke gentle ping this and #50803 are not time-sensitive but are blockery for further work.

@mroeschke mroeschke added this to the 2.0 milestone Jan 25, 2023
@mroeschke mroeschke merged commit dba96f9 into pandas-dev:main Jan 25, 2023
@mroeschke
Copy link
Member

Thanks @jbrockmendel

@jbrockmendel jbrockmendel deleted the ref-parsing-5 branch January 25, 2023 23:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mroeschke mroeschke mroeschke approved these changes

Assignees
No one assigned
Labels
Non-Nano datetime64/timedelta64 with non-nanosecond resolution Refactor Internal refactoring of code
Projects
None yet
Milestone
2.0
Development

Successfully merging this pull request may close these issues.
2 participants
@jbrockmendel @mroeschke