From acfffce48d88d2f2b78d0df79e60cdbf5d31d4bb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Sybren=20A=2E=20St=C3=BCvel?= <sybren@stuvel.eu>
Date: Thu, 19 Mar 2020 17:42:45 +0100
Subject: [PATCH] Configured Poetry to not use virtualenvs in `./.venv`

Having a virtualenv in `.venv` is very convenient because many tools
automatically pick up on it. However, this then also happens during the
construction of the Docker images, which subsequently breaks.

Until a proper fix is found, it's easiest to just put the virtualenv
outside of the project.
---
 poetry.toml | 2 ++
 1 file changed, 2 insertions(+)
 create mode 100644 poetry.toml

diff --git a/poetry.toml b/poetry.toml
new file mode 100644
index 0000000..c0c340a
--- /dev/null
+++ b/poetry.toml
@@ -0,0 +1,2 @@
+[virtualenvs]
+in-project = false