scrapinghub / scrapinghub/dateparser
Bad parsing of korean date
Open
Nobody has claimed this yet.
Type: Bug - Language
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 520
- Avg merge
- 22h 56m
- Merged PRs (30d)
- 6
Description
>>> parse("2013년 08월 14일", languages=["ko"])
Should be parsed as 2013-08-14.
>>> parse("2013.08.14 23시 54분", languages=["ko"])
datetime.datetime(2019, 11, 11, 11, 7, 49, 750793)
Should be parsed as 2013-08-14 23:54. It seems to be finding some sort of relative time.
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 two Korean examples with parse(..., languages=["ko"]) and compare the returned values with the expected dates. Done means the first input returns 2013-08-14 and the second returns 2013-08-14 23:54 instead of a relative date.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- localization
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100