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

Add support for Rye #629

Open
fpgmaas opened this issue Mar 21, 2024 · 0 comments
Open

Add support for Rye #629

fpgmaas opened this issue Mar 21, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@fpgmaas
Copy link
Owner

fpgmaas commented Mar 21, 2024

Is your feature request related to a problem? Please describe.

Rye is gaining a lot of popularity. As of writing, deptry does not support Rye properly, since it does not fetch development dependencies from tool.rye.dev-dependencies.

However, I can imagine that this flag is prone to change in the near future. For example astral-sh/rye#705 proposes to store dev dependencies under [project.optional-dependencies.dev], which would allow users to use the --pep621-dev-dependency-groups flag as proposed in this PR. Then there's also PEP 735 which proposes a new [dependency-groups] field, which would render special handling of Rye obsolete. And then there is also astral-sh/rye#705, which requests dependency groups. Although that does not speak directly of development dependencies, I can imagine that there is also a an ask to split development dependencies into groups (e.g. test and docs).

So this raises the question; should we simply add support for Rye's development dependencies in its current state, or do we give it some more time to see which direction the project is headed in?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant