mirror of https://github.com/sipwise/repoapi.git
When invoking `virtualenv --python=python3 virtualenv` to deploy the virtual environment, installing the python-debian wheel, and then re-executing `virtualenv --python=python3 virtualenv` once again, we might end up without the virtualenv/lib/python*/site-packages/debian directory, resulting in: | Traceback (most recent call last): | File "<string>", line 1, in <module> | ModuleNotFoundError: No module named 'debian' This is a bug in setuptools >=51.3.3-1, see https://bugs.debian.org/1041091 for the details, so currently affecting all systems with Debian/bookworm. By excluding installation of setuptools (via --no-setuptools), we would be able to work around this bootstrapping problem itself, though then installation of django-jsonify (which we depend on) fails with: | ModuleNotFoundError: No module named 'setuptools' Let's take this as a chance to switch from virtualenv to the more lightweight venv, quoting https://docs.python.org/3/library/venv.html: | Changed in version 3.5: The use of venv is now recommended for creating virtual environments. Change-Id: Iad06bf8c49abd96441ab04bb9b7e3917acd1ee59master
parent
b50fb86bcf
commit
983d11a11a
Loading…
Reference in new issue