Python environments are a common hidden cause of low disk space: .venv/ , caches, and build artifacts scale with every repo and experiment.

After a few months, it is easy to accumulate dozens of environments consuming gigabytes—and you only notice when something fails to install or your disk hits 0%.

This guide shows where the storage goes and a safe, inventory-first cleanup workflow across venv/pip/Poetry/conda/uv.

The silent growth nobody monitors

A virtual environment seems small at first, but it multiplies quickly:

test project

hackathon repo

tutorial clone

temporary branches

PoCs that never got closed

With realistic dependency management (frameworks, data libraries, tooling), each environment can consume hundreds of MB, even GB.

Where the technical junk hides

Not only in .venv/ :

cached Poetry environments

conda environments

.tox folders

scattered pycache directories

dist/build packaging artifacts

This set grows quietly because almost no default workflow cleans it…