From 98c6318326575412986cef7012961eacd9912977 Mon Sep 17 00:00:00 2001
From: MarkKoz <1515135+MarkKoz@users.noreply.github.com>
Date: Sun, 29 May 2022 10:55:04 -0700
Subject: Deps: use pip-tools instead of Pipenv

Pipenv was limited to only "normal" and "dev" dependencies. pip-tools
is more flexible, since each requirements file can be constrained by
more than one other requirements file. This means CI can choose to only
install coverage deps in the test job and linting deps in the lint job,
but these dependencies will still be constrained by each other and by
other requirements, so a developer will be able to install both sets
simultaneously without conflicts.

Use a Makefile to make up for the loss of Pipenv's scripts
functionality.
---
 requirements/coverage.pip | 10 ++++++++++
 1 file changed, 10 insertions(+)
 create mode 100644 requirements/coverage.pip

(limited to 'requirements/coverage.pip')

diff --git a/requirements/coverage.pip b/requirements/coverage.pip
new file mode 100644
index 0000000..fcc14da
--- /dev/null
+++ b/requirements/coverage.pip
@@ -0,0 +1,10 @@
+#
+# This file is autogenerated by pip-compile with python 3.10
+# To update, run:
+#
+#    pip-compile --output-file=requirements/coverage.pip requirements/coverage.in
+#
+coverage[toml]==6.4
+    # via -r requirements/coverage.in
+tomli==2.0.1
+    # via coverage
-- 
cgit v1.2.3