-
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
Depencendy listed in poetry.lock
is not installed
#4111
Comments
Hi, I encountered the same issue. Just FYI personally I don't have this issue with 1.1.4 and 1.1.5, it starts with 1.1.6. |
Thanks @ThomasRobertFr - can confirm that downgrading to |
Can confirm this issue is present in both 1.1.6 and also the pre-release 1.2.0a1 . Is this intended? |
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. |
EDIT: I does seem to be fixed in 1.2.0a1 though. |
@ThomasRobertFr just tried the testcase on my machine. I recreated the lockfile ( |
After a bit of additional testing it seems as even though locking works, the benefit of adding |
My bad, I don't know what I did wrong when I tried last time, but it does seem fixed, thanks a lot for trying and letting me know @bstadlbauer Regarding |
So not all of my dependencies are on the same file system level. E.g.:
And When doing a
in version 1.1.7. In version 1.1.5 this only happened when Again, a minimum example to reproduce this: |
Ah ok I see! So actually your problem comes from the fact that when installing 3rd package, the relative path I don't have this issue because I have a structure similar to your first example where all my dev packages are at the same level without the Hope this will be fixed soon, and good luck in your projects! |
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
Hi!
I currently have a project structure similar to:
Where
third_package
depends onsecond_package
which in turn depends onfirst_package
and first package depends onpsycopg2-binary = "2.8.5"
. The dependenciesthird_package
->second_package
as well assecond_package
->first_package
are created using a path dependency, wheredevelop
is set totrue
. E.g.:I set
develop
totrue
as this seems to mitigate #3368 (in the real usecase, these projects might have different root directories).When I now
poetry lock
in the third package, it looks as expected:Click to expand!
However, after a
poetry install
,psycopg2
is missing in the environment. This issue does not occur on one level of nesting (e.g.psycopg2
being a dependency ofsecond_package
)I added a zip of my minimum example if you would like to try this yourself:
poetry_dependency_bug.zip
The text was updated successfully, but these errors were encountered: