-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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 1.2.0 solves extra dependencies incorrectly #5999
Comments
works fine for me, given the provided
starlette is installed as expected @gabriel-ss did I misunderstand the repro? |
@dimbleby Thanks for the quick response! The issue does not occur in the package itself, but when you try to add it with poetry to another project. For example, if I try to add this package dep-with-extras-0.1.0.tar.gz — which was generated from the example pyproject — using
generating this lock:
This only occurs if there are multiple extras using the same optional dependecy. |
Nice. The issue is that whereas if we apply |
Awesome, just tested with the new fix and everything works flawlessly, thank you very much! |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
I am on the latest Poetry version.
I have searched the issues of this repo and believe that this is not a duplicate.
If an exception occurs when executing a command, I executed it again in debug mode (
-vvv
option).OS version and name: openSUSE Tumbleweed 20220630 on WSL
Poetry version: 1.2.0b
Link of a Gist with the contents of your pyproject.toml file: Dependency Example
Issue
When installing a package with optional dependencies that are present in multiple extras, the generated lock ends missing dependencies of dependencies. For example, when attempting to install a lib with the provided pyproject including the "api" extra, the project ends with fastapi in the lock, but misses starlette, which is a dependency of fastapi. Removing line 15 of the pyproject makes poetry resolve dependencies correctly again.
This behavior was observed only in the 1.2.0x versions of poetry. In 1.1.x everything works correctly.
The text was updated successfully, but these errors were encountered: