scrapinghub / scrapinghub/dateparser
Two ISO-8601 variants don't parse
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 520
- Avg merge
- 22h 56m
- Merged PRs (30d)
- 6
Description
Hi!
[version 1.0.0-1 (Debian).]
These variants of ISO-8601 (as produced by coreutil's date) for some reason don't parse:
python3 -c "import dateparser; print(dateparser.parse('$(date --iso-8601=hours)'));"
python3 -c "import dateparser; print(dateparser.parse('$(date --iso-8601=ns)'));"
(All other variants as described in date's man page work fine.)
Thx!
S
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the two dateparser.parse examples from the issue and inspect the ISO-8601 parsing entry points in the repository. Add regression coverage for the hours and nanoseconds variants, with completion defined as both examples returning parsed dates while existing ISO-8601 variants continue to pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100