python-poetry / python-poetry/poetry
install: support specific package installations
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 34.3k
- Forks
- 2.5k
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 30
Description
One of the common use case in a few scenarios (CI, Tox etc.) is to install an arbitrary set of packages as locked by poetry. While dependency groups aims to solve a pre-defined set, the flexibility of poetry install pkg1 pkg2 can be benfitial.
When poetry install pkg1 is used, we should install pkg1 similar to performing pip install pkg1 but using the pinned versions.
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 concerns the poetry install CLI entry point; begin by tracing how install arguments and locked package versions are currently handled. Define and test the behavior for poetry install pkg1, including installing only the requested package with its pinned version. Done means arbitrary requested packages work consistently for CI and Tox-style use cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100