Arie Bovenberg
Arie Bovenberg
The tagline for the library needs to be short, descriptive, and enticing. Some I can think of: - datetimes made correct and strict - datetimes defused and modernized - strict...
Many standards and libraries allow for times like `23:59:60` to represent leap seconds, **whenever** should too. (Note that this is not the same as taking into account historical leap seconds,...
It'd be useful to have some kind of recurrence/range type to indicate "every day", "every 3 weeks", or "every other month". Probably best to follow established standards (iCalendar, ISO8601) on...
Something that's quite common in datetime libraries is an 'interval' type. It's not the question whether such a thing could be implemented, but whether it is possible to define the...
Currently, the pickling format is rather straightforward, but inefficient. On the plus side, the format has been set up so backwards-compatible changes are possible in the future. This means we...
To understand the basics of the API at first glance, there should be a simple diagram which shows the different classes, their differences, and how to convert between them.
How to handle [this](https://tc39.es/proposal-temporal/docs/ambiguity.html#ambiguity-caused-by-permanent-changes-to-a-time-zone-definition) i.e. imagine you store `ZonedDateTime(2030, 3, 31, hour=1, tz='America/New_York')` which we expect to exist at this moment. However, by the time 2030 rolls around NYC has...
As a simplification, hyphenation is not performed on words consisting of multiple styles (e.g. "**com**pli*cated*"). This is a rare case, and I therefore skipped implementing it. If needed, it can...