use pipenv rather than pip install

Author: tlotze

.envrc

@@ -0,0 +1,4 @@
+layout pipenv
+# announce python version and show the path of the current python in ${PATH}
+echo "Virtualenv has been activated for $(python -V)"
+echo "Virtualenv dir: $(which python)"

.gitignore

@@ -13,6 +13,7 @@ sdist
 develop-eggs
 .installed.cfg
 src-mrd/
+.venv
 
 # Installer logs
 pip-log.txt

.gitlab-ci.yml

@@ -1,13 +1,12 @@
 before_script:
     - echo -e "[buildout]\nlogin = admin\npassword = admin" > secret.cfg
     - ln -fs local_ci.cfg local.cfg
-    - python3 -m venv .
-    - ./bin/pip install -r requirements.txt
+    - pipenv install
     - ./bin/develop up -f || true
     - ./bin/buildout -t 3 || ./bin/buildout -v
 
 job1:
   script:
     - export DISPLAY=:99
-    - ./bin/pre-commit run -a
+    - pipenv run pre-commit run -a
     - ./bin/test

CHANGES.rst

@@ -1,5 +1,10 @@
 Changes
 
+Unreleased
+==========
+
+- Use pipenv
+
 3.5
 ===
 - Remove temporarystorage for Plone 6.0 (local_coredev.cfg)

Pipfile

@@ -0,0 +1,14 @@
+[[source]]
+url = "https://pypi.org/simple"
+verify_ssl = true
+name = "pypi"
+
+[packages]
+setuptools = "==65.5.1"
+wheel = "==0.38.4"
+"zc.buildout" = "==3.0.1"
+
+[dev-packages]
+
+[requires]
+python_version = "3.11"

Pipfile.lock

@@ -53,25 +53,18 @@ Symlink to the file that best fits you local environment. At first that is usual
 
     ln -s local_develop.cfg local.cfg
 
-Create a virtualenv in Python 2.7 or Python 3.7 (Plone 5.2 only).
-
-.. code-block:: bash
-
-    virtualenv .  # for Python 2.7
-    python3.7 -m venv .  # for Python 3 (Plone 5.2 only)
-
 Install and configure Plone
 
 .. code-block:: bash
 
-    ./bin/pip install -r requirements.txt
-    ./bin/buildout
+    pipenv install
+    pipenv run buildout
 
 Install git pre-commit hooks
 
 .. code-block:: bash
 
-    ./bin/pre-commit install
+    pipenv run pre-commit install
 
 
 Structure
@@ -196,11 +189,11 @@ Symlink to the development-config:
 
 The development-setup will build a simple instance with some useful tools (see below). The setup assumes that zeo, varnish and loadbalancing are only configured on production.
 
-Install git pre-commit hooks using the pre-commit tool that was installed via requirements.txt:
+Install git pre-commit hooks using the pre-commit tool that was installed via pipenv:
 
 .. code-block:: bash
 
-    ./bin/pre-commit install
+    pipenv run pre-commit install
 
 
 Use in production