We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In poetry v2 (recently released), poetry recommend (see https://python-poetry.org/docs/dependency-specification/) moving the [tool.poetry.dependencies] section into project.dependencies, however other dependency groups still have to be specified within the tool.poetry section (for example tool.poetry.group.test.dependencies).
If I do that, then I get I900 errors for test dependencies.
I guess that the PEP621 method takes precedence over the poetry method (which probably doesn't take into account project.dependencies anyway).
Am guessing the logic rework to make this work as expected wouldn't be too difficult.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
In poetry v2 (recently released), poetry recommend (see https://python-poetry.org/docs/dependency-specification/) moving the [tool.poetry.dependencies] section into project.dependencies, however other dependency groups still have to be specified within the tool.poetry section (for example tool.poetry.group.test.dependencies).
If I do that, then I get I900 errors for test dependencies.
I guess that the PEP621 method takes precedence over the poetry method (which probably doesn't take into account project.dependencies anyway).
Am guessing the logic rework to make this work as expected wouldn't be too difficult.
The text was updated successfully, but these errors were encountered: