python-poetry / python-poetry/poetry-plugin-export

`poetry export --filter 'pytest,pytest-*'` or similar

Open
#236 0 comments 0 reactions 0 assignees View on GitHub

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 FAQ and general documentation and believe that my question is not already covered.

Feature Request

I am trying to figure out what would be the best way to combine poetry's dependency management with tox. I need to configure multiple environments for formatting, linting, testing, etc. and each of those environments has a different list of development dependencies. I think I could make it work by defining groups for dependencies but would it not be simpler to just be able to create any dynamic filter within tox, so that poetry does not need to be aware of those different groups, just that the dependencies are only for development?

This is why I suggest adding filtering functionality to poetry export so that one could do:

poetry export --only dev --filter 'pytest,pytest-*'

So that then tox's default handling of dependencies (via pip) can rely on dynamically generated locked dependencies' lists.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing poetry export command and its --only behavior, then examine how tox consumes dependency lists through pip. Define the filtering syntax and supported matching behavior before implementation. Done means an export can dynamically select matching development dependencies for tox environments and has coverage for the requested example.

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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.