Re: [go-nuts] Parsing time with timezones seem to fail

2023-02-13 Thread Sven Rebhan
a/Denver: > > denver, err := time.LoadLocation("America/Denver") > panicOn(err) > testParseLocation("2023-02-09 02:55:00", denver) > > b. Replace the ambiguity with an unambiguous numerical offset before > parsing: > > testParse("20

Re: [go-nuts] Parsing time with timezones seem to fail

2023-02-13 Thread Sven Rebhan
On Friday, February 10, 2023 at 7:45:37 PM UTC+1 Ian Lance Taylor wrote: But it's not the case that the timezone abbreviation is never taken into account. As the comment says, the timezone abbreviation is taken into account if it is defined for the current location. For example, if the current l

Re: [go-nuts] Parsing time with timezones seem to fail

2023-02-10 Thread Sven Rebhan
The issue here is that the timezone information is ignored when computing the timestamp *value.* Take the following examples layout := "2006-01-02 15:04:05 MST" mytimeMST, err := time.Parse(layout, "2023-02-09 02:55:00 MST") mytimeCET, err := time.Parse(layout, "2023-02-09 10:55:00 CET") Both