scrapinghub / scrapinghub/dateparser
Date after colon is not parsed (": 24 February 2019")
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
Date after colon is not parsed, e.g. : 24 February 2019
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 parsing input : 24 February 2019 with the dateparser package and trace the parser entry point that handles text after a colon. Confirm the corrected behavior with a regression test for this example; no specific source file or test path is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100