-
Notifications
You must be signed in to change notification settings - Fork 128
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
Issues Handling Parse of iso8601 datetime strings #53
Comments
@rwarren Thoughts? |
Not a fan of the tuple return. I think I have a solution that enables me to not have to venture outside of the delorean for handling naive times, though. It works like this:
What do you think? This is up and working. I'll send a PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently
delorean
parse function casts the bad (no timezone) version of the to utc.Although there is no way to know whether or not the UTC was provided like in the 2nd good option or it was a decision (assumption) made my
delorean
internally (I blame my OCD).Give a way to introspect this would be ideal. I would like to avoid providing naive datetimes being return by delorean but maybe a way to determine if assumptions were made.
Like so currently
Maybe this
The text was updated successfully, but these errors were encountered: