[InessaPawson]

Updates the pixi section to make clear that pixi add installs from conda channels by default and pixi add --pypi installs from PyPI, with a matching manifest example.
Closes #589.

[netlify]

✅ Deploy Preview for python-package-guide ready!

Name	Link
🔨 Latest commit	6bbdcf2
🔍 Latest deploy log	https://app.netlify.com/projects/python-package-guide/deploys/6af15acb121486b7f09ee584
😎 Deploy Preview	https://deploy-preview-819--python-package-guide.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[InessaPawson]

@ruben-arts We'd appreciate your feedback on this PR. 🙏

[ruben-arts]

This look great to me!

[lwasser]

@all-contributors please add @ruben-arts for review, docs

[allcontributors]

@lwasser

I've put up a pull request to add @ruben-arts! 🎉

[lwasser]

Suggested change

This is the same outcome as creating a conda environment, installing `numpy` and `gdal` with conda, and then running `pip install scipy` inside it. The difference is that the conda-vs-PyPI split is declared explicitly in the manifest and captured in the lock file, so there is no ambiguity about how a given dependency will be resolved at install time.

The above process, which created a Python environment using Pixi, produces the same outcome environment as you might do creating a conda environment using `conda create` and then installing `numpy` and `gdal` with conda, and then running `pip install scipy` inside it. The difference is that the conda-vs-PyPI split is declared explicitly in the manifest and captured in the lock file, so there is no ambiguity about how a given dependency will be resolved at install time.

[lwasser]

This statement is actually confusing too. You can add a pip: section to a conda environment. yml file. and that is explicit. Can you clarify what this actually does that is different from using an environment.yml file that has a pip section?

i think maybe leaning into the speed gains might be a better summary saying - this is similar to creating a conda environment with a pip section - so it's declarative but pixi adds

x, y, z value to. the process

Emphasize the similarities, but also how they differ and how Pixi gives you more power. @ruben-arts I'd love your input here because I am not a Pixi user, but this statement doesn't clearly articulate the value I think Pixi provides to a user!

[InessaPawson]

@lwasser The way I understand it, pixi has 4 main advantages:

1. One lock file. Unlike environment.yml, which is a spec, pixi.lock pins both conda and PyPI dependencies across all declared platforms.
2. Coordinated solve. Pixi solves conda dependencies first, then PyPI dependencies using uv, treating matching conda packages as locked to avoid duplicate installations and version conflicts.
3. Project-scoped envs. Environments live in .pixi/envs/. No manual activation needed with pixi run, or use pixi shell for an interactive session.
4. And yes, speed (it's built in Rust).

Thank you so much for the review, Leah! I’ll rewrite the paragraph to spell out those differences.

cc @ruben-arts

[lwasser]

I'd actually love some changes on this one to clarify the power of pixi vs just using conda. great additions here !!

[tkoyama010]

Awesome to add pixi! Thanks