scrapinghub / scrapinghub/dateparser
STRICT_PARSING use
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 520
- Avg merge
- 22h 56m
- Merged PRs (30d)
- 6
Description
BHello,
The STRICT_PARSING use is not so easy to understand.
Example with release 1.0.0
parse('90 days',settings={'STRICT_PARSING':True})
Result: datetime.datetime(2020, 8, 3, 16, 24, 8, 599042)
Same issue with search :
search.search_dates('90 days',settings={'STRICT_PARSING':True})
result: [('90 days', datetime.datetime(2020, 8, 3, 16, 27, 8, 382830))]
I expected None result
Or is it another solution to avoid relative date results ? Only if day, month and year are found.
Best Regards
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 by reproducing the reported parse() and search.search_dates() examples with STRICT_PARSING enabled. Trace where STRICT_PARSING is handled for relative dates; done means the behavior for inputs such as “90 days” matches the documented expectation, with regression coverage for both entry points.
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
- 45/100