Feature Request: Support for Adding Local Path Dependencies with Relative Paths in poetry add

[mike-live]

Hi Poetry Development Team,

I would like to suggest a feature enhancement for the poetry add command. Currently, when adding local packages, Poetry records the absolute path in the pyproject.toml. This can be inconvenient for project portability and clarity, especially when sharing or working across different environments using version control systems like git.

It would be highly beneficial if poetry add could accept relative paths and store them as relative in pyproject.toml by default or using flag. This would improve project maintainability and make dependency management more intuitive, particularly in monorepos or multi-package repositories.

Please consider adding support for this feature in future releases. Thank you for your ongoing efforts to improve Poetry!

[finswimmer]

Hey @mike-live,

if you want to use relative path dependencies you have to use the [tool.poetry] section to define your dependencies. If you do so, you can use poetry add to add a relative path dependencies to the pyproject.toml.

Within the [project] section path dependencies must always be absolut according to PEP 508.

Also see https://python-poetry.org/docs/dependency-specification/#path-dependencies

[mike-live]

Hi @finswimmer,

thank you for your assistance. May be it is possible implement the following behavior:

• poetry add --tool.poetry my_package adds my_package into section [tool.poetry],
• poetry add --project my_package adds my_package into section [project]

In this case I will be able to use best of both worlds: use relative dependencies for local packages and be able to install dependencies without poetry in some cases.

What do you think about it?

[radoering]

Just adding it to tool.poetry is not enough if there is project.dependencies. See #9474 (comment).