Repository navigation
Unclear that default setting of virtualenvs.in-project means that venvs are created in cache-dir #3709
Description
- I have searched the issues of this repo and believe that this is not a duplicate.
Issue
Can something be added to the virtualenvs.in-project setting documentation that mentions that without a .venv in the project and with the default value of virtualenvs.in-project that poetry install will create a venv under the directory
in cache-dir?
Reacted by Vance Morris
Activity
vmorris commentedon Mar 15, 2021
Wow thank you @tavor ... I was really scratching my head on this one.
Based on the documentation I was expecting
poetryto create a.venvwithin my project directory if one did not exist. Very confusing!finswimmer commentedon Mar 15, 2021
Maybe just copy the first sentence from here: https://python-poetry.org/docs/basic-usage/#using-your-virtual-environment to here: https://python-poetry.org/docs/configuration/#virtualenvsin-project-boolean ?
Secrus commentedon May 16, 2022
I think adding a short note, about the default path of virtualenvs when
virtualenvs.in-projectis set to false, would be enough. PRs on that are welcome.Changes in docs for Issues python-poetry#4800, python-poetry#3709, py…
Changes in docs for Issues #4800, #3709, #3573, #2211 and PR #2414 (#…
github-actions commentedon Mar 2, 2024
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.