scrapinghub / scrapinghub/dateparser
Should we add support for duplicate timezone info?
Open
Nobody has claimed this yet.
discussion
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 520
- Avg merge
- 22h 56m
- Merged PRs (30d)
- 6
Description
Sometimes the timezone info is duplicate:
'Mon, 25 Jun 2018 10:37:47 +0530 (GMT+05:30)'(source: https://github.com/scrapinghub/dateparser/issues/425)'2012-11-02 04:16:13.000123 PM EST (-05:00)'(source: https://github.com/scrapinghub/dateparser/issues/743)
and dateparser can't handle them. As this is used in some internet sources like the Gmail timestamp, should we add support for it?
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 example strings from the issue and tracing how dateparser handles timezone information. Done means both duplicate-timezone formats are parsed successfully without breaking existing date parsing behavior; no specific source file or test is named, so locate the relevant parser tests first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100