scrapinghub / scrapinghub/dateparser
Is there a way to control which century two digit years are parsed as?
Open
Nobody has claimed this yet.
Type: Enhancement
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 520
- Avg merge
- 22h 56m
- Merged PRs (30d)
- 6
Description
>>> import dateparser
>>> dateparser.parse('11/10/78')
datetime.datetime(1978, 11, 10, 0, 0)
>>> dateparser.parse('8/14/62')
datetime.datetime(2062, 8, 14, 0, 0)
Is there a simple way to tell dateparser to prefer a specific century for this kind of ambiguous date?
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 examples with dateparser.parse and inspect the parsing entry point and relevant tests for two-digit years. Determine where a century preference could be represented and define completion as a configurable behavior that handles both examples consistently, with tests covering the selected century.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100