scrapinghub / scrapinghub/dateparser
Import very slow
Open
Nobody has claimed this yet.
performance
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 520
- Avg merge
- 22h 56m
- Merged PRs (30d)
- 6
Description
I figured that the import of this library is very slow (500-1000ms on my system).
Given that the library probably less complex than e.g. numpy or similarly large packages: Do you think the import times can be optimized in some way?
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
No files, tests, or entry points are identified in the issue. Start by profiling the library's import path and measuring its current 500–1000 ms import time; done means a demonstrably faster import without breaking existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100