-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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.1.6 does not resolve dependencies for "nested"package in develop mode #3956
Comments
Poetry is very nice tool to manage python dependencies! Unfortunately the problem prevent us to upgrade to the new version 1.1.6. I can reproduce problems with nested dependency resolution as well. With the following steps you can reproduce the problem with nested git dependencies without develop mode. # checkout repository
git clone https://github.com/marns93/test-poetry-nested-deps-1.git
# ensure old poetry version is installed
poetry self update 1.1.5
# install dependencies with old poetry version
poetry install
# update poetry
poetry self update 1.1.6
# try to install dependencies as well
poetry install Now you can see that all dependencies of the nested git dependency (test-poetry-nested-deps-3) will be removed. # rollback to old version
poetry self update 1.1.5
# try to install dependencies again
poetry install The nested git dependencies will be installed. If there is no @abn Could you please have a look? Thanks! |
The root cause has been identified (see #4202) and this will be fixed in the next bugfix release. Note that you will to regenerate the lock file for the fix to take effect. |
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. |
-vvv
option).Issue
In case you have such dependencies:
proj1 -> proj2 -> proj3
marked as develop, newest poetry (1.1.6) will not install proj3 dependencies whether previous release will handle that case. This occurs ONLY ifpoetry.lock
is present.To reproduce:
The text was updated successfully, but these errors were encountered: