-
-
Notifications
You must be signed in to change notification settings - Fork 667
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
Unexpected date parsing #434
Labels
Comments
Looks like it's being interpreted as an epoch time. 2016 seconds is a bit over 33 minutes.
…On May 2, 2017 12:01:33 AM EDT, "Radim Řehůřek" ***@***.***> wrote:
Weird bugs were tracked to Arrow parsing dates incorrectly (and
silently):
```python
>>> import arrow
>>> arrow.get('2016')
<Arrow [1970-01-01T00:33:36+00:00]>
```
Is that expected/intended? What is Arrow interpreting the string `2016`
as?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#434
|
I have another example that indicates arrow doing greedy matching and producing wrong results:
In the first example it matches incorrectly with |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Weird bugs were tracked to Arrow parsing dates incorrectly (and silently):
Is that expected/intended? What is Arrow interpreting the string
2016
as?Also, this was not what I expected:
Format order matters, and if order wrong, produce silent errors?
The text was updated successfully, but these errors were encountered: