-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
WIP/ENH: Pass tzinfos to dateutil parser #24104
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
Hello @jbrockmendel! Thanks for submitting the PR.
|
huh? what is this supposed to accomplish from a user POV ? |
At the moment we aren't correctly parsing any timezones aside from UTC offsets.
(yes, yes, I know "CST" isn't a timezone. But PST, CST, EST, ... are not uncommon in the wild) |
that’s not my point how is this actually useful? |
Because it allows users to parse date-like strings correctly. Because at the moment we are silently returning incorrect results (well, dateutil is issuing a warning). Because before long dateutil will start raising in these cases and we should provide some way of letting users pass a |
this is a really tiny edge case and adds lots of complexity |
I agree that this adds complexity, but not that it is a tiny corner case. Let's put this on the back-burner until after 0.24.0. |
ok, prob best to close this. and simply create a project for those issues. |
Closing until after 0.24.0 |
Putting this up early because the
set_option
behavior deserves discussion. The alternative is to make/let users passtzinfos
in Timestamp, to_datetime, DatetimeIndex, and probably others.git diff upstream/master -u -- "*.py" | flake8 --diff
Still need to: