Why is manual venv creation advised rather than usage of pipx?

[RokeJulianLockhart]

1. https://github.com/samschott/maestral/blob/5dba3d1544447bffc00b8fc8b936b99444030efe/README.md#python-package-using-pypi:~:text=python3%20-m%20pip%20install%20--upgrade%20maestral advises:

   python3 -m pip install --upgrade maestral

   RokeJulianLockhart@s1e8h4:~> python3 -m pip install --upgrade maestral
   error: externally-managed-environment
   
   × This environment is externally managed
   ╰─> To install Python packages system-wide, try
       zypper install python311-xyz, where xyz is the package
       you are trying to install.
       
       If you wish to install a non-rpm packaged Python package,
       create a virtual environment using python3.11 -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-rpm packaged Python application,
       it may be easiest to use `pipx install xyz`, which will manage a
       virtual environment for you. Install pipx via `zypper install python311-pipx` .
   
   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.
   RokeJulianLockhart@s1e8h4:~>
   

2. However, that does not work, so following python3's advice, I performed:

   pipx install maestral

   RokeJulianLockhart@s1e8h4:~> pipx install maestral
     installed package maestral 1.8.0, installed using Python 3.11.5
     These apps are now globally available
       - maestral
   done! ✨ 🌟 ✨
   

   which worked.

[samschott]

Mostly because I'm not at all familiar with pipx, and venv is part of the Python standard lib.