Go to file
Bradlee Speice 7bb02a7648 Licensing/docs updates 2018-06-17 23:31:25 -04:00
src Ignore tests needing relativedelta 2018-06-17 22:55:48 -04:00
tests Ignore tests needing relativedelta 2018-06-17 22:55:48 -04:00
.gitignore tzinfos isn't Vec<String> 2018-06-07 23:17:23 -04:00
.travis.yml Use python codegen to generate the tests 2018-06-12 22:22:30 -04:00
Cargo.toml Licensing/docs updates 2018-06-17 23:31:25 -04:00
LICENSE Licensing/docs updates 2018-06-17 23:31:25 -04:00
README.md Get the README updated with what's needed before 1.0 2018-06-17 23:21:11 -04:00
build_pycompat.py Ignore tests needing relativedelta 2018-06-17 22:55:48 -04:00

README.md

dtparse

A dateutil-compatible timestamp parser for Rust

Where it stands

The library works really well at the moment, and passes the vast majority of dateutils parser test suite. This isn't mission-critical ready, but is more than ready for hobbyist projects.

The issues to be resolved before version 1.0:

Functionality:

  1. We don't support weekday parsing. In the Python side this is accomplished via dateutil.relativedelta

  2. Named timezones aren't supported very well. 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.

  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

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.