--no-directory option seems not to be working

[elben10]

• Poetry version: 1.4.2
• Python version: 3.10.8
• OS version and name: Linux 80afcc38dfa0 5.10.104-linuxkit
• pyproject.toml: https://gist.github.com/elben10/cd1d5dfc18a1ea15de2771a622219adc

• 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

--no-directory seems to not be working (introduced in #6845). When i run the following command it raises the following error.
poetry install --no-root --no-directory
Path /src/dummy for dummy does not exist

As I understand it, the sole purpose of the option is to ignore directory dependencies. I have followed the example in FAQ. The dockerfile is also included in the gist

[Secrus]

Pretty sure your path should be relative. As you can see in the error message, it is currently searching in the root directory /.

[elben10]

It is correct that the current directory is the root, but the package is added relative to that (poetry add -e src/dummy). The reason that the current directory is the root is that it is run within a docker container. The default working directory of the python image is the root

[Secrus]

Summoning @radoering @adriangb since they were the ones working on this.

[dimbleby]

you did not provide your poetry.lock

[elben10]

It is now included in the gist

[dimbleby]

@adriangb

[adriangb]

See #7923

[dimbleby]

aha. Looks close, just wants the testcases to be fixed...?

[adriangb]

Yes, and I'm a bit tied up this week unfortunately since we really want to make a V2 beta release for Pydantic. Only so much OSS one can handle 😅.

[dimbleby]

maybe an unfortunate coincidence that poetry 1.5.0 is also imminent - it would be a shame to include this new function, broken on release. I'll leave a note in the 1.5.0 tracking issue so that someone can at least make a deliberate decision.

[radoering]

@elben10 I just merged the fix into master. Can you try again, please?

[elben10]

Works as expected. Thanks for the quick resolution

[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.