scrapinghub / scrapinghub/dateparser
STRICT_PARSING failed with MM/YYYY format
Open
Nobody has claimed this yet.
Status: Bug confirmed
Type: Bug
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 520
- Avg merge
- 22h 56m
- Merged PRs (30d)
- 6
Description
Hi,
I've noticed dateparser.parse("10/2017", settings={"STRICT_PARSING": True}) gives datetime.datetime(2017, 10, 10, 0, 0).
Is this the intended behavior? (even if the input string is missing a component) Are there any workarounds if I'd want it to output None?
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 provided dateparser.parse call with the STRICT_PARSING setting and the MM/YYYY input. Trace how incomplete dates are handled and establish whether the intended result is None; done means the behavior is decided and covered consistently for this example.
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
- 35/100