From ea55e5cc2c98d168ce4708da0ebeb19eab857b80 Mon Sep 17 00:00:00 2001
From: Davi Gray <124840911+Davi-Gray@users.noreply.github.com>
Date: Thu, 22 Jun 2023 19:34:02 -0500
Subject: [PATCH] Clarify use of virtualenvs.in-project setting.

---
 docs/configuration.md | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/docs/configuration.md b/docs/configuration.md
index d9c074262c3..9b88d326c62 100644
--- a/docs/configuration.md
+++ b/docs/configuration.md
@@ -309,12 +309,18 @@ might contain additional Python packages as well.
 
 Create the virtualenv inside the project's root directory.
 
-If not set explicitly, `poetry` by default will create virtual environment under
-`{cache-dir}/virtualenvs` or use the `{project-dir}/.venv` directory when one is available.
+If not set explicitly, `poetry` by default will create a virtual environment under
+`{cache-dir}/virtualenvs` or use the `{project-dir}/.venv` directory if one already exists.
 
 If set to `true`, the virtualenv will be created and expected in a folder named
 `.venv` within the root directory of the project.
 
+{{% note %}}
+If a virtual environment has already been created for the project under `{cache-dir}/virtualenvs`, setting this variable to `true` will not cause `poetry` to create or use a local virtual environment.
+
+In order for this setting to take effect for a project already in that state, you must delete the virtual environment folder located in `{cache-dir}/virtualenvs`.
+{{% /note %}}
+
 If set to `false`, `poetry` will ignore any existing `.venv` directory.
 
 ### `virtualenvs.options.always-copy`