2018-06-04 22:21:29 -04:00
|
|
|
# dtparse
|
2018-07-24 23:36:11 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-06-04 22:21:29 -04:00
|
|
|
A [dateutil](https://github.com/dateutil/dateutil)-compatible timestamp parser for Rust
|
|
|
|
|
|
|
|
|
|
## Where it stands
|
|
|
|
|
|
2018-06-17 23:21:11 -04:00
|
|
|
The library works really well at the moment, and passes the vast majority of `dateutil`s parser
|
|
|
|
|
test suite. This isn't mission-critical ready, but is more than ready for hobbyist projects.
|
2018-06-04 22:21:29 -04:00
|
|
|
|
2018-06-17 23:21:11 -04:00
|
|
|
The issues to be resolved before version 1.0:
|
|
|
|
|
|
|
|
|
|
**Functionality**:
|
|
|
|
|
|
2018-06-24 23:56:06 -04:00
|
|
|
1. ~~We don't support weekday parsing. In the Python side this is accomplished via `dateutil.relativedelta`~~
|
2018-06-24 23:55:14 -04:00
|
|
|
Supported in v0.8
|
2018-06-17 23:21:11 -04:00
|
|
|
|
|
|
|
|
2. Named timezones aren't supported very well. [chrono_tz](https://github.com/chronotope/chrono-tz)
|
|
|
|
|
theoretically would provide support, but I'd also like some helper things available (e.g. "EST" is not a named zone in `chrono-tz`).
|
|
|
|
|
Explicit time zones (i.e. "00:00:00 -0300") are working as expected.
|
|
|
|
|
|
2018-07-08 21:54:28 -04:00
|
|
|
3. ~~"Fuzzy" and "Fuzzy with tokens" modes haven't been tested. The code should work, but I need to get the
|
|
|
|
|
test cases added to the auto-generation suite~~
|
2018-06-17 23:21:11 -04:00
|
|
|
|
|
|
|
|
**Non-functional**: This library is intended to be a direct port from Python, and thus the code
|
|
|
|
|
looks a lot more like Python than it does Rust. There are a ton of `TODO` comments in the code
|
|
|
|
|
that need cleaned up, things that could be converted to enums, etc.
|
|
|
|
|
|
|
|
|
|
In addition, some more documentation would be incredibly helpful. It's, uh, sparse at the moment.
|
