scrapinghub / scrapinghub/dateparser
Parsing incorrect dates - inconsistencies
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 520
- Avg merge
- 22h 56m
- Merged PRs (30d)
- 6
Description
Why
parse("2021-01-13", settings={'DATE_ORDER': 'YDM'}) return None
but
parse("2021-13-01", settings={'DATE_ORDER': 'YMD'}) return datetime.datetime(2021, 1, 13, 0, 0)
dateparser 1.1.8
Python 3.11.5
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
Start at the public parse(...) entry point and reproduce both DATE_ORDER examples from the issue on Python 3.11.5 with dateparser 1.1.8. Trace how YDM and YMD are interpreted, then define the expected consistent behavior and add regression coverage before verifying both inputs.
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
- Needs clarification
- Newbie friendliness
- 35/100