Further Reading: Libraries and Virtual Environments

Virtual Environments and Package Management

Python Documentation: "Virtual Environments and Packages" Tutorial. (Tier 1) The official Python tutorial on venv and pip. Concise, authoritative, and always up-to-date with the latest Python version. Start here for any questions about venv syntax or behavior. https://docs.python.org/3/tutorial/venv.html
Python Documentation: venv — Creation of Virtual Environments. (Tier 1) The full module reference for venv, including advanced options like --system-site-packages, --clear, and --upgrade-deps. More detailed than the tutorial. https://docs.python.org/3/library/venv.html
Python Packaging User Guide: "Installing Packages." (Tier 1) The official guide from the Python Packaging Authority (PyPA). Covers pip, virtual environments, requirements.txt, and pyproject.toml with clear examples. This is the canonical reference for Python packaging. https://packaging.python.org/en/latest/tutorials/installing-packages/
Python Packaging User Guide: "Managing Application Dependencies." (Tier 1) Walks through the full workflow of creating an application, managing its dependencies, and preparing it for deployment. Includes guidance on when to use requirements.txt vs. pyproject.toml. https://packaging.python.org/en/latest/tutorials/managing-dependencies/

pip Documentation: User Guide. (Tier 1) The complete reference for pip commands, configuration, and behavior. Especially useful: the sections on requirements file format, version specifiers, and dependency resolution. https://pip.pypa.io/en/stable/user_guide/
pip-tools Documentation. (Tier 2) pip-tools provides pip-compile (generates pinned requirements.txt from a requirements.in with loose constraints) and pip-sync (ensures your environment matches the requirements file exactly). A step up from basic pip for serious projects. https://pip-tools.readthedocs.io/
Poetry Documentation. (Tier 2) Poetry is an alternative to pip + venv that handles virtual environment creation, dependency resolution, and package publishing in one tool. Its pyproject.toml-based workflow is increasingly popular in the Python community. https://python-poetry.org/docs/
Conda Documentation: "Managing Environments." (Tier 2) Conda is the package manager used in the Anaconda distribution, popular in data science and scientific computing. Unlike pip, conda can install non-Python dependencies (C libraries, R packages). Worth knowing if you're heading into data science. https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html

semver.org. (Tier 1) The specification for Semantic Versioning 2.0.0. Short, clear, and definitive. If you want to understand exactly what MAJOR.MINOR.PATCH means and the rules for incrementing each, this is the source. https://semver.org/
Python Documentation: PEP 440 — Version Identification and Dependency Specification. (Tier 2) Python's version numbering scheme, which is compatible with but slightly different from strict semver. Covers pre-releases, post-releases, dev releases, and the version specifiers used in requirements.txt and pyproject.toml. https://peps.python.org/pep-0440/

Birsan, A. (2021). "Dependency Confusion: How I Hacked Into Apple, Microsoft, and Dozens of Other Companies." (Tier 1) The blog post that introduced the "dependency confusion" attack to the world. Accessible writing with concrete examples. Eye-opening for anyone who uses pip. https://medium.com/@alex.birsan/dependency-confusion-4a5d60fec610
Python Software Foundation: "Securing PyPI." (Tier 1) The PSF's initiatives to secure the Python package ecosystem, including Trusted Publishers, two-factor authentication for maintainers, and malware detection. Understanding these protections helps you evaluate the trustworthiness of packages. https://pypi.org/security/
Snyk: "State of Open Source Security" Report. (Tier 2) An annual report covering vulnerabilities in open-source packages across all major ecosystems, including Python. Good for understanding the broader landscape of supply chain security. https://snyk.io/reports/open-source-security/

Requests Documentation. (Tier 1) Beautifully written documentation for the most popular Python HTTP library. The "Quickstart" guide is one of the best examples of library documentation in the Python ecosystem. https://requests.readthedocs.io/
pandas Documentation: "Getting Started Tutorials." (Tier 1) A gentle introduction to pandas DataFrames. Start with the "10 Minutes to pandas" tutorial if you want a quick overview, or work through the full getting-started series for a thorough introduction. https://pandas.pydata.org/docs/getting_started/
matplotlib: "Tutorials." (Tier 1) Matplotlib's official tutorials, organized from introductory to advanced. The "Pyplot tutorial" covers the basics you need for most visualizations. https://matplotlib.org/stable/tutorials/
Rich Documentation. (Tier 1) The rich library's documentation includes a gallery of output examples, making it easy to see what's possible. The "Introduction" page is a great starting point. https://rich.readthedocs.io/
Flask Tutorial: "Quickstart." (Tier 2) Flask's quickstart guide walks you through creating your first web application in about 20 minutes. A natural next step if web development interests you. https://flask.palletsprojects.com/en/latest/quickstart/

Collins, K. (2016). "How one programmer broke the internet by deleting a tiny piece of code." Quartz. (Tier 1) The original reporting on the left-pad incident. Clear, non-technical writing that captures the absurdity and the lessons. https://qz.com/646467/how-one-programmer-broke-the-internet-by-deleting-a-tiny-piece-of-code
Williams, C. (2016). "How one developer just mass mass mass broke Node, Babel and thousands of projects." The Register. (Tier 1) Technical reporting with more detail about the dependency chains involved. Good for understanding the cascade effect.

Horstmann, C. (2020). "The Cathedral and the Bazaar at 20: What Open Source Taught Us." IEEE Software. (Tier 2) A reflection on open-source software development that provides context for why package ecosystems like PyPI exist and how community-maintained code works.
Python Documentation: PEP 518 — Specifying Minimum Build System Requirements. (Tier 2) The PEP that introduced pyproject.toml as a standard configuration file for Python projects. Technical but important if you want to understand why pyproject.toml replaced setup.py. https://peps.python.org/pep-0518/