From: tadayoshi funaba <redmine@...>
Date: 2011-06-07T20:12:27+09:00
Subject: [ruby-core:36813] [Ruby 1.9 - Bug #4776][Rejected] DateTime.new! has been disabled


Issue #4776 has been updated by tadayoshi funaba.

Status changed from Open to Rejected

not a bug.

it's for only internal use.
he must have known it.
i once talked to the authour of tzinfo about Rational.new!.

anyway now DateTime.new! is not reasonable at all.
it does not depend on the current internal structure.
it is not fast if avairable.

learn good manners.
----------------------------------------
Bug #4776: DateTime.new! has been disabled
http://redmine.ruby-lang.org/issues/4776

Author: Aaron Patterson
Status: Rejected
Priority: Normal
Assignee: tadayoshi funaba
Category: 
Target version: 
ruby -v: ruby 1.9.3dev (2011-06-06 trunk 31944) [x86_64-darwin10.7.0]


After r31668, `DateTime.new!` no longer works.  Is there a replacement?  Or is this a mistake?

This code works before r31668, but breaks after 31668:

irb(main):001:0> require 'date'
=> true
irb(main):002:0> DateTime.new!
NoMethodError: undefined method `new!' for DateTime:Class
	from (irb):2
	from /Users/aaron/.local/bin/irb:12:in `<main>'
irb(main):003:0>

Some gems (specifically the tzinfo gem) depend on this method.  Rails depends on tzinfo, and since tzinfo breaks I can no longer test trunk against rails. :-(


-- 
http://redmine.ruby-lang.org