Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

poetry export --filter 'pytest,pytest-*' or similar #236

Open
2 tasks done
king-of-poppk opened this issue Oct 4, 2023 · 0 comments
Open
2 tasks done

poetry export --filter 'pytest,pytest-*' or similar #236

king-of-poppk opened this issue Oct 4, 2023 · 0 comments

Comments

@king-of-poppk
Copy link

  • 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.

@Secrus Secrus transferred this issue from python-poetry/poetry Oct 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant