Issue #9794 has been updated by Felipe Contreras. Tadayoshi you are so fucking ridiculous it's not even funny. You reject a perfectly sensible patch that **EVERYBODY** agrees with for NO REASON AT ALL WHATSOEVER? At the very list give a reason. I'm amazed that anybody would make you a maintainer of anything. It's because of attitudes like this that I'm not surprised that the Ruby language has trouble competing with languages like Python; you just have a nonsensical culture. I am still waiting for **A REASON**. ---------------------------------------- Bug #9794: DateTime.strptime() doesn't work correctly for '%s %z' https://bugs.ruby-lang.org/issues/9794#change-46455 * Author: Felipe Contreras * Status: Rejected * Priority: Low * Assignee: tadayoshi funaba * Category: ext * Target version: * ruby -v: 2.1.1p76 * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN ---------------------------------------- Time.strptime() works correctly: Time.strptime('0 +0100', '%s %z').strftime('%s %z') => "0 +0100" But DateTime.strptime() doesn't: DateTime.strptime('0 +0100', '%s %z').strftime('%s %z') => "0 +0000" In Rubinious it does work correctly: DateTime.strptime('0 +0100', '%s %z').strftime('%s %z') => "0 +0100" This make the RubySL date space fail: DateTime#strptime parses seconds and timezone correctly FAILED Expected "1970-01-01T00:00:00+00:00" to equal "1970-01-01T01:00:00+01:00" In addition, both C and perl preserver the offset correctly when doing '%s %z'. So it's very clear DateTime.strptime() has to be fixed. Patch attached. ---Files-------------------------------- 0001-datetime-fix-strptime-s-z.patch (1.94 KB) -- https://bugs.ruby-lang.org/