mirror-github-bspeice/dtparse
1
0
Fork 0
mirror of https://github.com/bspeice/dtparse synced 2024-11-13 17:38:09 -05:00
Code Issues Releases Wiki Activity
95 Commits 2 Branches 8 Tags 467 KiB
Rust 88.8%
Python 11.2%
v0.9.1
Go to file
Bradlee Speice 848f1b9249 Release 0.9.1
2018-07-19 23:05:03 -04:00
fuzz Fix typo in the fuzzer script 2018-07-18 22:38:02 -04:00
src Improve error message to match dateutil 2018-07-18 23:03:53 -04:00
.gitignore Don't track pyc 2018-07-02 22:23:55 -04:00
.travis.yml Use python codegen to generate the tests 2018-06-12 22:22:30 -04:00
build_pycompat_tokenizer.py Redo the tokenization 2018-07-08 14:30:48 -04:00
build_pycompat.py testFuzzyAMPMProblem is causing us issues 2018-07-08 15:23:51 -04:00
Cargo.toml Release 0.9.1 2018-07-19 23:05:03 -04:00
LICENSE Licensing/docs updates 2018-06-17 23:31:25 -04:00
README.md Fuzzy mode is now tested 2018-07-08 21:54:28 -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 Supported in v0.8

  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.