Open slequeux opened 1 year ago
Poetry version: 1.1.13
please try again with recent poetry
as reported against 1.1.13 this duplicates #3085 and #4884 - which were closed on the grounds that #6843 resolved them
however I don't think that #6843 actually did resolve this, so I guess this can stay open and it's all good. (Good from a tracking point of view I mean; of course a bug is still a bug.)
I'm able to reproduce this on v1.5.1
Just ran into this on v1.7.1
My workflow was:
poetry install
develop = true
poetry lock --no-update
poetry.lock
correctly includes the develop = true
flag for that dependencypoetry update
No dependencies to install or update
-vvv
option) and have included the output below.Issue
I have 2 poetry projects, one depending on another, using a path dependency.
First I did not included the
develop = true
file and was facing the issue that it was difficult to work on a feature that requires modifications on these 2 projects as modification on the dependency was not replicated to my virtualenv.I updated my dependency with the
develop = true
part and ran apoetry update
. This had no effect. I had to completely delete the virtualenv and recreate it to have an effect.Steps to reproduce:
project-lib = { path = "../project-lib" }
poetry install
on both, virtual envs are correctly created and the code in "project-lib" can be used in the other one.project-lib = { path = "../project-lib", develop = true }
poetry update
, one can see that the lock file is updatedHere I would expect to see changes in the lib from the other project. I can't see them. Once the virtual env has completely been recreated, then any change in the lib can be seen in the other project.
My guess here is that in one mode (develop = false), the module is installed in the virtualenv and not in the other mode (develop = true), but changing mode do not remove the module from the virtualenv as it should do.