Motivation for using Python virtual environments for easy sharing

README.md

Understanding Python virtual environments

High Level Introductions

• Is UV the FUTURE of Python PACKAGING? 🐍📦, by Hynek Schlawack
• Which Python Package Manager Should You Use?

Articles

• How virtual environments work by Brett Cannon
• Why you should use python -m pip by Brett Cannon

GitHub Issues Explaining What To Do / Not To Do

• Why not to use sudo for installs and to use virtual environments by Henry Schreiner (in GitHub Issue "Package with pyproject.toml cannot be installed with pip install -e")

Code With Anthony videos

• virtualenv vs. venv (beginner - intermediate) anthony explains #040
• how to get pip for deadsnakes / docker pythons (intermediate) anthony explains #293
• simple python dockerfile w/ flask (intermediate) anthony explains #296

Code examples

• pyhf CUDA enabled Docker images

Understanding non-system Python installations

You should treat the version of Python that comes installed with your operating system as being off-limits to you to use — it is the operating system's and only the operating system's. This "system Python" or "platform Python" exists for the OS to run programs it controls and all user code and programs should be run with a different Python runtime that you install by yourself.

Articles

• Managing Multiple Python Versions With pyenv by Logan Jones on RealPython

Understanding Packaging and Package Maintenance

• App vs Library by Henry Schreiner
• Semantic Versioning Will Not Save You by Hynek Schlawack
• Should You Use Upper Bound Version Constraints? by Henry Schreiner
• Why you shouldn't invoke setup.py directly by Paul Ganssle