managing-environments

Create isolated development environments using venv or Conda to prevent package conflicts. Each project gets its own environment, ensuring dependencies don't interfere with system packages or other projects. Activate the environment before installing to keep installations contained and reproducible.

Run `python -m venv .venv` to create an isolated environment, then activate it with `source .venv/bin/activate` (Linux/Mac) or the Windows equivalent. After activation, install project dependencies safely within that isolated space without affecting other projects.

Environment detection checks whether venv or Conda is currently active and reports its status before installation. Always confirm the active environment matches your project before proceeding with package installation to avoid installing into the wrong location.

Both venv and Conda create isolated Python environments. Conda manages system-level dependencies alongside Python packages, making it better for complex scientific stacks. Venv is lighter and sufficient for pure-Python projects. Choose based on your project's dependency complexity and platform needs.

Import issues often stem from installing packages in the wrong environment or missing installations. Validate your active environment, verify packages are installed there, and recreate the environment from documented dependencies to restore reproducibility and resolve import failures.

Documenting environment creation steps—venv commands, Python versions, and dependency lists—ensures reproducibility across team members and machines. This prevents 'works on my machine' problems and lets others replicate your exact setup and dependency versions.