From: parkrmoore@...
Date: 2014-12-30T03:36:29+00:00
Subject: [ruby-core:67218] [ruby-trunk - Bug #10677] Regression: Time#parse no longer automatically converts to localtime

Issue #10677 has been updated by Parker M.


Ok, thanks Nobuyoshi. Is this documented somewhere? It caused a lot of strife for me, and I don't think I'll be the only one. I wrote a [short post about it](https://byparker.com/blog/2014/ruby-2-2-0-time-parse-localtime-regression/) as I had no clue this was scheduled as a bug fix. I'll update my post with a link to the original bug and the related fixes. Thanks!

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

* 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/