Open fanconnie opened 10 months ago
I don't think that this qualifies as a bug, as this is by design. The comments in the implementation specify that parse_time
expects a golang-style timestamp format:
https://github.com/google/starlark-go/blob/dded03209eade82b7ee3c5eac52796a853c46c58/lib/time/time.go#L32-L36
So the literal string "RFC3339"
isn't going to work either, but fortunately the default format to parse_time
is the golang-style format string for an RFC3339 timestamp ("2006-01-02T15:04:05Z07:00"
)
This package exists only in the Go implementation. In hindsight exposing this very Go-centric API for time formatting was perhaps a mistake, and if other implementations (Java, Rust) were to want a time package we should probably revisit it.
This package exists only in the Go implementation. In hindsight exposing this very Go-centric API for time formatting was perhaps a mistake, and if other implementations (Java, Rust) were to want a time package we should probably revisit it.
OK:
https://github.com/bazelbuild/bazel/issues/19477
https://github.com/facebookexperimental/starlark-rust/issues/95
Errors for format=
RFC3339
or%Y-%m-%dT%H:%M:%S.%f