DateTime yaml bug

Hi,

does anybody know a quick fix to the DateTime or Yaml bug

YAML::load(DateTime.now.to_yaml).class
=> Time

Thx

Artur

On 27 Aug., 12:09, Artur M. [email protected] wrote:

Hi,

does anybody know a quick fix to the DateTime or Yaml bug

YAML::load(DateTime.now.to_yaml).class
=> Time

Nobody out there to answer the question? The Problem is
not only, that the class switches to Time, but also that
the read in date is wrong by an week (and the time differs too):

dt= DateTime.now
=> #<DateTime: 21205505265589/8640000,1/12,2299161>

dt.to_yaml
=> “— !timestamp 2007-08-28T11:17:35+0200\n”

res= YAML::load(dt.to_yaml)
=> Mon Aug 20 05:17:35 Westeurop ische Normalzeit 2007

res.to_yaml
=> “— 2007-08-20 05:17:35 +02:00\n”

using Marshal

Marshal.load(Marshal.dump(dt))

gives the right solution (both the class and the data in it are
exactly the same), but I really wanted to stick to yaml …

Artur

From: Artur M. [mailto:[email protected]]

> does anybody know a quick fix to the DateTime or Yaml bug

>

> YAML::load(DateTime.now.to_yaml).class

> => Time

cannot help you, but only say that i can replicate the behaviour here
too. someone complained too
http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/262969

i think it’s a bug. stick to marshall in the meantime.

kind regards -botp

On Aug 27, 2007, at 03:10, Artur M. wrote:

does anybody know a quick fix to the DateTime or Yaml bug

YAML::load(DateTime.now.to_yaml).class
=> Time

Please file a bug in the ruby tracker on RubyForge.

Also:

irb(main):003:0> DateTime.parse ‘3000/01/01 01:01:01’
=> #<DateTime: 243370443661/86400,0,2299161>
irb(main):004:0> dt = _
=> #<DateTime: 243370443661/86400,0,2299161>
irb(main):005:0> YAML.load dt.to_yaml
ArgumentError: time out of range

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs