python-poetry / python-poetry/poetry-plugin-export
export - ability to chose subset of dependencies to export
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 335
- Forks
- 57
- Avg merge
- 1h 23m
- Merged PRs (30d)
- 3
Description
- I have searched the issues of this repo and believe that this is not a duplicate.
- I have searched the documentation and believe that my question is not covered.
Feature Request
The use case I'm thinking of here is CI pipelines and dev dependencies.
Most of the time I don't need all dev dependencies for a build. For example, I might use black and flake8 locally but only want to run unit tests in my CI build, in which case installing black and flake8 on a CI box just adds time.
In terms of CLI, thinking something like
poetry export -f requirements.txt --ignore black flake8 > requirements.txt
n.b. I'm not looking to export only dev deps (like https://github.com/python-poetry/poetry/issues/1441) but rather a way to selectively exclude deps (dev or prod).
Contributor guide
No contributing guide indexed for this repository
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 with the poetry export -f requirements.txt command shown in the issue and trace how dependencies are selected for export. Define how selectively excluding both development and production dependencies should work, then verify the resulting requirements output for the example excluding black and flake8.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100