dongsimu4422 2016-09-16 19:55
浏览 118

为什么go用本地位置而不是UTC解析我的时间戳

I don't understand this behaviour (or the doc) of this: https://play.golang.org/p/vz2UTz-3Yy

On the playground, it return the expected results:

t = 2015-06-01 00:00:00 +0000 UTC
t.Location() = UTC
parsed = 2015-06-01 00:00:00 +0000 UTC
parsed.Location() = UTC

On my mac, I get:

t = 2015-06-01 00:00:00 +0000 +0000
t.Location() =
parsed = 2015-06-01 00:00:00 +0000 +0000
parsed.Location() =

The problem is, if I create a date with

time.Date(2015, time.June, 01, 00, 0, 0, 0, time.UTC)

the 2 times are different, because one has a location ("UTC"), and the other not (or "Local"). I'm bit lost here.

Thanks

  • 写回答

1条回答 默认 最新

  • drlma06060 2016-09-16 20:08
    关注

    When parsing a time with a zone offset like -0700, if the offset corresponds to a time zone used by the current location (Local), then Parse uses that location and zone in the returned time. Otherwise it records the time as being in a fabricated location with time fixed at the given zone offset. [time.Parse]

    t.Location (a name) is only set when the local offset matches the offset that is in the parsed date string. You probably have a different time zone set.

    So the offset is recorded but the location is not looked up.

    评论

报告相同问题?

悬赏问题

  • ¥15 乘性高斯噪声在深度学习网络中的应用
  • ¥15 运筹学排序问题中的在线排序
  • ¥15 关于docker部署flink集成hadoop的yarn,请教个问题 flink启动yarn-session.sh连不上hadoop,这个整了好几天一直不行,求帮忙看一下怎么解决
  • ¥30 求一段fortran代码用IVF编译运行的结果
  • ¥15 深度学习根据CNN网络模型,搭建BP模型并训练MNIST数据集
  • ¥15 C++ 头文件/宏冲突问题解决
  • ¥15 用comsol模拟大气湍流通过底部加热(温度不同)的腔体
  • ¥50 安卓adb backup备份子用户应用数据失败
  • ¥20 有人能用聚类分析帮我分析一下文本内容嘛
  • ¥30 python代码,帮调试,帮帮忙吧