apertium / apertium/apertium-init
Switch to pipenv
Open
enhancement
gci
- Dominant language
- Python
- Stars
- 9
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
See https://github.com/apertium/streamparser/pull/33 for an approach.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the approach in apertium/streamparser pull request 33, then inspect the apertium-init repository to determine which dependency and setup files are affected. Done means the project uses pipenv consistently for its bootstrap scripts and the existing setup flow still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100