Discussion: Should `llm` keep `pip` as a dependency?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12.5k
- Forks
- 998
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 10
Description
I understand why, because you have an embedded venv manager for all of the llm-* python packages, but maybe requiring pip isn't the best way, and should just throw an error message instead? If they managed to install it, the main thing enforcing that pip exists, is pip itself.
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 reviewing how the embedded virtual-environment manager installs or requires pip and how missing pip is currently handled. Decide whether pip should remain a dependency or be replaced with an error path, then define tests that demonstrate the chosen behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100