Widen/Opening-up dependency versions
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 64/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- build-system
Research direction
Start by locating the dependency declaration file and reviewing the currently pinned or capped versions. Identify which ceilings can be widened without changing the requested dependency set, then verify that Mighty still installs alongside other packages and that the existing test suite passes.
Written by the indexing model from the issue text.
Description
Currently the dependencies have very narrow versions specified, making it very hard to install Mighty alongside other packages. As we discussed last year, opening up the ceilings of dependency versions would be great.
- Dominant language
- Python
- Stars
- 61
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
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.
More from automl/Mighty
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Optimize repo tree Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Implement PQN Openenhancement
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100