The following error popped up during our CI builds on MacOS:
$ pip3 install mako
shell: /bin/bash -e {0}
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try brew install
xyz, where xyz is the package you are trying to
install.
If you wish to install a non-brew-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip.
If you wish to install a non-brew packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
PEP668 tries to help people to prevent dependency issues on their systems.
We can be pretty sure that our controlled CI environment is not affected by this issue. Thus, we can use --break-system-packages and install system-wide.
We introduced the FlyCI runner in #752 to enable CI runs on MacOS/ARM. This PR fixes a Python dependency install issue. Further, it installs liborc via brew install orc to test and install ORC kernels.
The following error popped up during our CI builds on MacOS:
PEP668 tries to help people to prevent dependency issues on their systems. We can be pretty sure that our controlled CI environment is not affected by this issue. Thus, we can use
--break-system-packages
and install system-wide.We introduced the FlyCI runner in #752 to enable CI runs on MacOS/ARM. This PR fixes a Python dependency install issue. Further, it installs liborc via
brew install orc
to test and install ORC kernels.