Project

General

Profile

Bug #14860

Time.strptime does not work with Julian dates using %j

Added by ajrkerr (Adam Kerr) about 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
[ruby-core:87545]

Description

Time.strptime does not appear to be handling Julian dates, it is defaulting the date to be whatever is provided as "now" (e.g. January 1). I believe this is because Time is calling Date._strptime which returns a hash with {:yday=> ...} and does not handle the yday keyword.

Found in 2.3.3, verified not working in 2.5.1.

require "time"
require "date"

### Works for Dates ###
parsed_date = Date.strptime("15300", "%y%j")
expected_date = Date.new(2015, 10, 27)
# Does not raise
raise "dates not equal" if expected_date != parsed_date


### Does not work for Time ###
parsed_time = Time.strptime("15300", "%y%j")
expected_time = Time.new(2015, 10, 27)
# Raises
raise "times not equal" if expected_time != parsed_time

Related issues

Related to Ruby master - Bug #15776: Difference between Time.parse behaviour between 2.6.0 and 2.6.1+Rejectednobu (Nobuyoshi Nakada)Actions
Has duplicate Ruby master - Bug #14933: Time.strptime with ordinal datesClosedActions
#1

Updated by nobu (Nobuyoshi Nakada) almost 2 years ago

  • Has duplicate Bug #14933: Time.strptime with ordinal dates added
#2

Updated by nobu (Nobuyoshi Nakada) almost 2 years ago

  • Status changed from Open to Closed

Applied in changeset trunk|r64028.


time.rb: yday support

  • lib/time.rb (Time.make_time): added yday support. [ruby-core:87545] [Bug #14860]
#3

Updated by nagachika (Tomoyuki Chikanaga) over 1 year ago

  • Backport changed from 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN to 2.3: REQUIRED, 2.4: REQUIRED, 2.5: REQUIRED
#4

Updated by nobu (Nobuyoshi Nakada) about 1 year ago

  • Related to Bug #15776: Difference between Time.parse behaviour between 2.6.0 and 2.6.1+ added

Also available in: Atom PDF