On Tue, Nov 22, 2016 at 10:30 AM, <david.clari...@mixpanel.com> wrote: > > Ignoring the TZ abbreviation when it doesn't happen to be the local TZ seems > like somewhat undesirable behavior. Unfortunately I can't work around this > by switching to numeric zones, since I'm not in control of the input I'm > parsing. Is there a fundamental reason time.Parse() couldn't interpret all > the TZ codes standardized in RFC-822? It seems time.LoadLocation(..) knows > about them. I'll make this suggestion on the issue you filed.
I replied on the issue. I note that if you know that the RFC 822 abbreviations are correct for your use case, despite the fact that they are ambiguous internationally, then you can use a simple string substitution to replace those abbreviations with the equivalent numeric timezone. Ian -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
