Use a single pip install command on startup
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11
- Forks
- 39
- Avg merge
- 18d 18h
- Merged PRs (30d)
- 1
Description
oci_env calls pip in multiple places multiple times. Pip is not meant to be used that way wand will happily create conflicts with already installed packages or update otherwise pinned dependencies.
Consolidating all calls to pip install into a single one can be considered a hard blocker for using it in any kind of CI.
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 locating the startup path in oci_env and every place that invokes pip install. Trace how those calls affect already installed and pinned dependencies, then consolidate them into one installation step and verify the result in the project's CI workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100