scrapinghub / scrapinghub/dateparser
`dateparser.search.search_dates` is confused by too many time references
Open
Nobody has claimed this yet.
search_dates
Type: Bug
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 520
- Avg merge
- 22h 56m
- Merged PRs (30d)
- 6
Description
I am on the latest version of the library, the test string is Now arriving today by 10 PM which gets parsed as
[('Now', datetime.datetime(2021, 10, 11, 7, 52, 27, 643936)), ('today', datetime.datetime(2021, 10, 11, 7, 52, 27, 647292)), ('10 PM', datetime.datetime(2021, 10, 11, 22, 0))]
While I would expect the magic to return only one date which is today at 10 pm.
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 dateparser.search.search_dates call with Now arriving today by 10 PM and inspect the search implementation and its existing tests. Done means the input returns only one date, representing today at 10 PM, without separate results for Now or today.
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