fpgmaas/deptry

Retrieve development dependencies from all dependencies groups in Poetry

mkniewallner opened this issue · 3 comments

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

On projects using Poetry, only [tool.poetry.dev-dependencies] and [tool.poetry.group.dev.dependencies] are considered for retrieving development dependencies.

Since groups only work locally, it is probably safe to assume that dependencies in all groups are development dependencies, regarding of the group. This would also be in line with what we do for PDM, where all dependencies groups are parsed.

Describe the solution you would like

Instead of just parsing [tool.poetry.dev-dependencies] and [tool.poetry.group.dev.dependencies], deptry should parse [tool.poetry.dev-dependencies] and all [tool.poetry.group.<group>.dependencies] to retrieve development dependencies.

Additional context

There might be reasons for users to opt-out from reading dependencies from specific groups (for instance, a specific group that defines dependencies only used by a CI workflow), but we could consider implementing that only if this is a feature that is requested by users.