`poetry install` installs the project as a dependency of itself?

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

Question

TL;DR: Is it expected behaviour when doing poetry install for the project to install itself as a dependency of itself?

I have started a new project using poetry init and followed up by poetry adding all my dependencies. I then pushed, and then cloned the git repo to another PC.

After the clone, I opened the new folder and did poetry install in that folder. That created the new virtual environment, as expected, but it also seems as if it installed the project as a dependency of itself. Please see the screenshot below. This is also evident in the new egg-info folder that was created. I expected the installations to stop at the last package (requests).

I did not expect that behaviour and would like to confirm if that is the intention of poetry install. You can find my project files here:

• pyproject.toml
• poetry.lock

[skorokithakis]

@sdispater Do you know when this might be released? I am about to introduce poetry at our company and I think this behavior would hinder adoption, maybe I can wait a bit if the feature is coming soon.

[skorokithakis]

I would also like to vote for an option to not install the project. Furthermore, the documentation is currently inaccurate, as poetry list says about install: “Installs the project dependencies.”

I, and I think most other people, understand this to mean that it does not install the project itself.

My use case for this is that I mainly develop Django applications, and whenever I run poetry install I only want the dependencies to be installed, and not the project itself (as that does not make sense for my use case).