python-poetry / python-poetry/poetry
Activate `requires-plugins` from a project without using `poetry install`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 34.3k
- Forks
- 2.5k
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 30
Description
Issue Kind
Change in current behaviour
Description
I have a use case where I currently copy the pypoetry.toml and poetry.lock files into a docker container and then run poetry export. In order to install the export plugin, I looked at using the tool.poetry.requires-plugins section, but it looks like that's only checked when the project is installed. It'd be nice if there was a way to ensure all required project plugins were installed without installing the project itself. That could either be a new command or maybe poetry self install could be changed to install project plugins as well.
Impact
This would improve the flexibilty of the tool.poetry.requires-plugins configuration option.
Workarounds
I worked around the issue by installing poetry-plugin-export explicitly in my dockerfile, but it'd be nice if there was a more generic way to accomplish this.
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 tracing how tool.poetry.requires-plugins is handled during project installation, then compare the existing poetry export and poetry self install command flows. Done means project plugins can be installed without installing the project itself; the issue leaves the preferred command or implementation path open.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100