scrapinghub / scrapinghub/dateparser
Fallback to the builtin re module when regex is not available
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 520
- Avg merge
- 22h 56m
- Merged PRs (30d)
- 6
Description
I'm deploying a project on a service that requires all the dependencies to be written in pure Python, C dependent libraries such as pandas are not supported.
I've noticed that regex depends on C, but seems just to be a drop-in replacement for the built-in re module. Does it make sense to catch an ImportError and fall back to the built-in one?
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
The issue names no files or tests; begin by locating where the regex dependency is imported and how dependencies are declared, then inspect existing tests for regex-backed behavior. Done means the parser still handles its covered cases when only Python's builtin re is available, with tests documenting the fallback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100