René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[DOC] [BLD] Building / developing matplotlib with uv \u0026 pixi","articleBody":"I've been slowly converting all my personal repos to use [uv](https://docs.astral.sh/uv/) for dependency management, and gave it a shot on matplotlib to see if it'd work. The below works right out of the box for me:\n\n```bash\n# Create a virtual environment with uv\nuv venv .venv\n\n# Activate the environment (optional, uv commands will automatically use the venv)\nsource .venv/bin/activate  # Linux/macOS\n# or: .venv\\Scripts\\activate  # Windows\n\n# Install dev dependencies\nuv pip install -r requirements/dev/dev-requirements.txt\n\n# Install matplotlib in editable mode\nuv pip install --no-build-isolation --editable \".[dev]\"\n\n# Verify installation\nuv run python -c \"import matplotlib; print(matplotlib.__file__)\"\n```\n\nThen I just point my VSCode python interpreter to the one in the .venv and everything works well. Note that a `uv sync` workflow does not work, given our somewhat custom build setup.\n\nI'm ambivalent about adding this as an option to the [development setup instructions](https://matplotlib.org/devdocs/devel/development_setup.html), since the `pip` commands throughout would need a toggle. I'm also unclear what sort of CI we use to ensure build instructions work as-written. But figured it was worth sharing here in case people want to use this approach.","author":{"url":"https://github.com/scottshambaugh","@type":"Person","name":"scottshambaugh"},"datePublished":"2025-12-18T04:59:10.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":28},"url":"https://github.com/30877/matplotlib/issues/30877"}