Poetry 1.0.10 -> 1.1.4: Files added to local repository are not referenced

Let’s say you have an index.html file you want to put along your Python code.

$ find .
pyproject.toml
package
package/foo.py

You do poetry install like that, before index.html exists.

Then you add it.

$ find .
pyproject.toml
package
package/foo.py
package/index.html

Now with 1.1.4, foo.py cannot see a index.html next to it. In 1.0.10 this worked fine. If you run poetry install after adding the index.html file, it installs nothing new and does not do what I intend.

If the index.html file exists before the very first poetry install, it seems to be fine.

I presume something with the way the virtual environments are made has been changed.

[sinoroc]

As the console output shows: “No dependencies to install or update”. So the new files are not installed. You would need to poetry run python -m pip uninstall subpackage, or bump the version number for subpackage.

But wait…

Read this: https://python-poetry.org/docs/dependency-specification/#path-dependencies

Before poetry 1.1 directory path dependencies were installed in editable mode by default. You should set the develop attribute explicitly, to make sure the behavior is the same for all poetry versions.

That is what changed for you between 1.0.10 and 1.1.4. I guess you relied on the editable installation of path dependencies. But now path dependencies are not installed as editable by default any more. So you would need something like that in your pyproject.toml:

[tool.poetry.dependencies]
python = "^3.8"
subpackage = {path = "packages/subpackage", develop = true}

[gitpushdashf]

It works!!!

Actually, the issue I noticed was in converting an existing virtualenv from non-develop to develop (or I guess vice versa). Which, admittedly could be pretty dicey.

I’ll close this out. Thank you so much for your help.