Issue #16031 has been updated by sawa (Tsuyoshi Sawada).


Perhaps, an option to chose between the two kinds of behavior may be useful. Something like `exception:`.

----------------------------------------
Bug #16031: Inconsistency between Date::strptime and Time::strptime at the end of a month
https://bugs.ruby-lang.org/issues/16031#change-80314

* Author: aliism (Ali Ismayilov)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-darwin18]
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
When parsing an invalid date, like February 31 or November 31, I get different results from Date and Time classes.
``` ruby
require 'date'
require 'time'

Date.strptime('2019-02-31', '%Y-%m-%d')
# Traceback (most recent call last):
#         5: from /Users/ali/.rbenv/versions/2.6.3/bin/irb:23:in `<main>'
#         4: from /Users/ali/.rbenv/versions/2.6.3/bin/irb:23:in `load'
#         3: from /Users/ali/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/irb-1.0.0/exe/irb:11:in `<top (required)>'
#         2: from (irb):5
#         1: from (irb):5:in `strptime'
# ArgumentError (invalid date)

Time.strptime('2019-02-31', '%Y-%m-%d')
# => 2019-03-03 00:00:00 +0100
```

I'd expect Time class to throw ArgumentError, just like the Date class.



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>