poetry update not updating included local packages

Consider the following directory structure:

poetry-package/
├── foo
│   └── foo.py
├── pyproject.toml
└── setup.py

Where foo.py is empty, setup.py is simply:

from setuptools import setup

setup(name='foo-package', version='0.0.1', packages=['foo'])

and pyproject.toml looks like:

[tool.poetry]
name = "foo-package-dev"
version = "0.1.0"
description = ""
authors = ["Your Name <[e-mail]>"]
packages = [{include = "foo"}]

[tool.poetry.dependencies]
python = "^3.8"

[tool.poetry.dev-dependencies]

[build-system]
requires = ["poetry>=0.12"]
build-backend = "poetry.masonry.api"

If I now run poetry install then the local foo-package version 0.0.1 is correctly installed since poetry run pip list gives:

Package     Version Location
----------- ------- ----------------------------------
foo-package 0.0.1   /home/pedro/Desktop/poetry-package
pip         19.2.3
setuptools  41.2.0

However if I now modify the setup.py bumping the version from 0.0.1 to 0.0.2 and then run poetry update the local package is not updated. On the other hand if run poetry install then the local package does indeed get updated (as per poetry run pip list). So my question is: is this a bug or a feature? I would’ve expected the update command to actually update the local included package but that isn’t the case.

For the record I’m using poetry version 1.0.5

[neersighted]

It’s still unclear what was being asked/requested here, or what is expected to happen. Poetry is not designed to be used with setuptools to manage the same project. The only reason that poetry install even triggers anything related to setup.py at all is for legacy technical reasons that we are migrating away from. poetry update does not interact with a setup.py at all, quite properly.

If you have a use case you think requires this, I would suggest creating a Discussion or joining Discord to see if others can help you use pure Poetry, or if Poetry is not the right tool for your project.

[petobens]

My use case finswimmer is that I want to install a non-poetry project with poetry. So I would like to run poetry within the project and not outside of it (and use the relative paths suggested by you). In this scenario I was wondering why is it that poetry update doesn’t update the package dependencies.