From: nobu@...
Date: 2015-01-04T07:47:10+00:00
Subject: [ruby-core:67322] [ruby-trunk - Bug #10677] Regression: Time#parse no longer automatically converts to localtime

Issue #10677 has been updated by Nobuyoshi Nakada.


Ben Johnson wrote:
> I have a strong feeling this is going to be a **major** problem as people try to move forward. Adding "local" time everywhere you use Time.parse simply is not feasible. This change is also outside of the scope of a "minor" version change for ruby.

I strongly disagree.
It's a bug that had ignored a part of the input which should not be ignored, and should be fixed as usual.


----------------------------------------
Bug #10677: Regression: Time#parse no longer automatically converts to localtime
https://bugs.ruby-lang.org/issues/10677#change-50781

* Author: Parker M
* Status: Rejected
* Priority: Normal
* Assignee: Zachary Scott
* Category: lib
* Target version: current: 2.2.0
* ruby -v: ruby 2.2.0p0 (2014-12-25 revision 49005) [x86_64-darwin14]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
In Ruby 2.1 and before, `Time#parse` automatically converted to the localtime:

Ruby 2.1:

~~~ruby
>> require 'time'
=> true
>> ENV['TZ'] = 'Australia/Melbourne'
=> "Australia/Melbourne"
>> Time.parse("2014-12-29 20:16:32 -0400")
=> 2014-12-30 11:16:32 +1100
~~~

But in Ruby 2.2, this is not the case:

~~~ruby
>> require 'time'
>> ENV['TZ'] = 'Australia/Melbourne'
>> Time.parse("2014-12-29 20:16:32 -0400")
=> 2014-12-29 20:16:32 -0400 # !!
>> Time.parse("2014-12-29 20:16:32 -0400").localtime
=> 2014-12-30 11:16:32 +1100
~~~

This seems to be a regression, as this is a change in default behaviour without a `MAJOR` version bump, violating semver.



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