Project

General

Profile

Bug #16031

Inconsistency between Date::strptime and Time::strptime at the end of a month

Added by aliism (Ali Ismayilov) 4 months ago. Updated 4 months ago.

Status:
Open
Priority:
Normal
Assignee:
-
Target version:
-
ruby -v:
ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-darwin18]
[ruby-core:94079]

Description

When parsing an invalid date, like February 31 or November 31, I get different results from Date and Time classes.

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.

History

Updated by sawa (Tsuyoshi Sawada) 4 months ago

Perhaps, an option to chose between the two kinds of behavior may be useful for both Date and Time. Something like exception: (true raises exception) or rollover: (true suppresses exception).

Also available in: Atom PDF