-
A lot of the Russian time zones are out of date. The UTC offsets are for their 2011 to 2014 DST-365 rules. They are now standard time 365, so each of those time zones is one hour off in its offset.
-
In several places in the guidance for resolving ambiguous `DateTime` values (both in [this doc](https://learn.microsoft.com/dotnet/standard/datetime/resolve-ambiguous-times) and [this doc](https://lea…
-
Some terms (especially media `timestamp` and `eventStart` and `eventEnd`) could benefit from expressing milliseconds. Ideally we support 4 ways of writing timestamps (all ISO):
```ini
2013-11-23T…
-
The [`IntoPy` implementation](https://github.com/PyO3/pyo3/blob/edf47b575ffe01d8357fa91bd471815a17f1a3a6/src/conversions/chrono.rs#L232C23-L232C23) for `chrono::DateTime` is implemented generically fo…
-
There's an incoming change in AsciiDoc Python to add a "use-utc" option that will set dates in UTC instead of local time. We should do the same in Asciidoctor. See https://github.com/asciidoc/asciidoc…
-
simple_logger v4.2.0
Using:
```rust
simple_logger::SimpleLogger::new()
.with_level(log::LevelFilter::Warn)
.with_local_timestamps()
.with_colors(stdout().is_termi…
-
Code here:
https://github.com/rtfeldman/elm-iso8601-date-strings/blob/3587ff12251261514d0da49837f3c170d0249448/src/Iso8601.elm#L342-L345
Might be:
```elm
multiplier * (hours * 60 + minutes)
```
-
**Describe the bug**
I was trying to understand how `shape` command works, as it's undocumented largely, and discovered that:
1. `move` command interrupts shape, dividing it into subshapes
2. `cl…
-
I am not able to parse timezones other an `Z`/`+00:00` with dtparse 1.3.2.
```python
>>> dtparse.parse("2021-05-04 13:37:00+00:00", "%Y-%m-%d %H:%M:%S%:z")
datetime.datetime(2021, 5, 4, 13, 37)
…
-
### Background and motivation
Very commonly, a `DateTime` needs to be converted to a `DateTimeOffset` with regard to a specific time zone. There is no built-in mechanism for doing so, and an imple…