managing-python-dependencies

First detect the project's dependency manager by checking for signal files like uv.lock, pyproject.toml, Pipfile, or requirements.txt. Then use that tool's install command, such as `uv add` or `poetry add`, instead of a global `pip install`.

Do not choose manually; follow the project's existing tooling. Check for uv.lock or [tool.uv] first, then [tool.poetry] in pyproject.toml, then Pipfile, then environment.yml, and default to venv plus pip with requirements.txt if none exist.

No, global pip installs are prohibited because they bypass project isolation and corrupt dependency state. Always use the project's detected manager or an explicit virtual environment path like `.venv/bin/pip`.

Default to venv plus pip: create an environment with `python3 -m venv .venv`, install packages via `.venv/bin/pip install`, and preserve state by running `.venv/bin/pip freeze > requirements.txt`.

Mixing tools bypasses the lockfile maintained by Poetry or uv, causing version drift and unreproducible environments. Always use the manager's own add command so the lockfile stays synchronized with installed packages.