-
Would it be possible to use ISO8601 standard timestamps instead of another different format?
ptman updated
8 years ago
-
`date.ParseISO("2018-02-02T00:00:00Z")`
should not fail.
-
[](https://xkcd.com/1179/)
I'm fine with having it as an option, but why use a custom format?
-
This was tested with the latest `main` from Elastic-Agent and Beats
The default logger (user configurable) and the events logger are using different formats for the timestamp:
Default logger (RFC333…
-
# Bug report
### Bug description:
```python
>>> datetime.fromisoformat('2020-01-01T00:00+00:90')
datetime.datetime(2020, 1, 1, 0, 0, tzinfo=datetime.timezone(datetime.timedelta(seconds=5400)))
```
…
-
Hi there,
first of all huge thanks for creating and maintaining this project. Just stumbled upon it recently
and it improved the API documentation I'm creating a lot!!!
I'm having the need to c…
-
## Nginx
記述確認
```bash
nginx -t
```
`etc/nginx/nginx.conf`
```diff
- access_log /var/log/nginx/access.log;
+ log_format json escape=json '{"time":"$time_iso8601",'
+ …
-
Support the latest ISO8601 specification.
Noteworthy changes:
* Week of year - Day of week calendar
* `YYYY-Www-D`
* Extended duration format
* `PYYYY-MM-DDThh:mm:ss`
-
Hello,
I would like to know if it is possible to parse `iso8601` duration time format? I've tried to parse `"P0Y0M0DT0H5M52.352S" or "P0Y0M0DT0H0M14.976S"` without success.
Regards,
Maxim
-
Unless I missed something, it seems like only Unix timestamps are supported for now. It would be useful to also support ISO8601 timestamps, e.g. "2014-02-11T10:22:46Z".