You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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
anddocs
).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?
The text was updated successfully, but these errors were encountered: