No error raised on invalid dates
See original GitHub issueIt seems like an error should be thrown on invalid dates, but this doesn’t appear to happen. Is there some parameter I need to pass in to the get()
function to enforce these are checked properly?
Using v0.12.1:
In [21]: import arrow
In [22]: arrow.get('2/30/2018')
Out[22]: <Arrow [2018-01-01T00:00:00+00:00]>
In [23]: arrow.get('13/4/2045')
Out[23]: <Arrow [2045-01-01T00:00:00+00:00]>
Issue Analytics
- State:
- Created 6 years ago
- Reactions:6
- Comments:5
Top Results From Across the Web
Why is the expected exception not thrown on parsing invalid ...
This question already has answers here: I get two strings and I must transform them into dates and show the difference in days...
Read more >10 Handling PL/SQL Errors
For example, PL/SQL raises the predefined exception NO_DATA_FOUND if a SELECT INTO statement returns no rows. You can use the pragma EXCEPTION_INIT to...
Read more >Exception condition "Date invalid" raised - SAP Community
Hello Experts,. While releasing thedata for a particular material from APO to ECC, the queues are seen jammed in /SAPAPO/CQ & showing the ......
Read more >Timex parsing invalid dates and the db is blowing up
But my little logic does not catch that and timex seems to parse it all ... (exit) an exception was raised: ** (ErlangError)...
Read more >Date::Error exception when viewing audit logs for an invalid date
No tasks are currently assigned. Use tasks to break down this issue into smaller parts. Linked items. 0.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I would count dates in the format “MM/DD/YYYY” as invalid for now.
@Luca409 @ryantuck I have submitted a pull request for this issue here: #527 Feel free to give it a review!