poetry-core does not install local dependency in editable mode

[bersbersbers]

• Poetry version: poetry_core-1.9.0-py3-none-any.whl

• Python version: 3.12.2

• OS version and name: Windows 11 22H2

• I am on the latest stable Poetry version, installed using a recommended method.

• I have searched the issues of this repo and believe that this is not a duplicate.

• I have consulted the FAQ and blog for any relevant entries or release notes.

• If an exception occurs when executing a command, I executed it again in debug mode (-vvv option) and have included the output below.

Issue

C:\Code\MyTestParent
│   pyproject.toml
│   TestParent.py
└───MyTestChild
        pyproject.toml
        TestChild.py

Both .py files are empty. The pyproject.toml files are:

MyTestParent:

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

[tool.poetry]
name = "TestParent"
version = "0.0.0"
description = ""
authors = []

[tool.poetry.dependencies]
python = ">=3.12"
TestChild = { path = "MyTestChild", develop = true }

MyTestChild:

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

[tool.poetry]
name = "TestChild"
version = "0.0.0"
description = ""
authors = []

[tool.poetry.dependencies]
python = ">=3.12"

Now, I can install TestParent in editable mode, but TestChild is not installed in editable mode:

$ pip install -e . && (pip list | findstr Test)
TestChild  0.0.0
TestParent 0.0.0   C:\Code\MyTestParent

[dimbleby]

there is no way to express in TestParent's metadata that TestChild is editable, this is expected

please close

[bersbersbers]

there is no way to express in TestParent's metadata that TestChild is editable

I think I don't get it. What is the purpose of the develop key in TestParents TestChild dependency then, if not to make it editable?

[dimbleby]

Poetry understands the poetry-specific configuration, poetry install will do what you want.

pip installcannot

[bersbersbers]

Is there any place that I could have learned about this before opening this issue? Or should this limitation be documented somewhere?

[dimbleby]

If you had followed the documentation you never would have typed pip install.

If you have a docs improvement in mind then no doubt that contribution would be welcome.

Either way, please close this one out.

[bersbersbers]

If you had followed the documentation you never would have typed pip install.

That implication is incorrect. https://github.com/python-poetry/poetry-core?tab=readme-ov-file#usage gives examples (only) using pip install.

[dimbleby]

Poetry docs are at https://python-poetry.org/docs/, the poetry-core GitHub repository is not the expected entry point.

Either way, please close this out and feel free to submit improvements in whatever place it is that confused you

[bersbersbers]

Poetry docs are at https://python-poetry.org/docs/

That is correct, and I would have filed this issue in https://pypi.org/project/poetry-core/ if that repository had issues enabled. Also, the "Bug tracker" link at https://pypi.org/project/poetry-core/ points ... here.

the poetry-core GitHub repository is not the expected entry point.

First, that is a weird thing to say in the age of web search engines, really. But as a user of poetry-core, what would you propose should my entry point be, if not that repository?

feel free to submit improvements in whatever place it is that confused you

I don't think I am confused at all. I may have a lack of knowledge, and all I am (still kindly, I hope) asking for is a reference for the kind of limitation you have cited above.

[dimbleby]

if you want to understand the interface between front-ends and back-ends you should read the python packaging specifications. But this is not something that most users will want to get into.

[bersbersbers]

... read the python packaging specifications. But this is not something that most users will want to get into.

Exactly. That is why I am suggesting that documented poetry functionality that silently fails in poetry core due to limitations of this interface be documented as not working in poetry core.

[dimbleby]

I don't know how to say it another way: docs improvements are welcome, please contribute the change you would like to see.

Meanwhile there is no bug here, please close this issue

[bersbersbers]

See #8971.

[github-actions]

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.