A New Way to Manage Python Environments
summary
pixi claims a single binary that bridges conda and pip, auto-generates reproducible lock-files and runs on Windows Mac and Linux; it uses a rust implementation, a CDCL-based solver, parallel downloads, hard-link caching and aggressive cache reuse so dozens of environments share one cache; current alpha supports PyPi resolution via a two-step conda→pip resolver and produces pixie.lock with exact platform artifacts; installer is one executable, package installs use hard links and parallel fetches for noticeably faster setup. single binary rust automatic lock-files hard-link caching
AI-written summary · about
chapters (17)
- 0:00Pixie and Prefix intro
- 1:03Python env challenges
- 2:48Pixie’s goals and demo
- 4:14Pixie features
- 5:59Existing tools comparison
- 8:52Pixie env creation
- 11:20Pixie history and Rust
- 13:03Pixie dependency resolution
- 14:27Pixie installation and caching
- 15:09Pixie.toml config
- 16:52Lock files and reproducibility
- 17:56Env activation and helpers
- 18:37Pip package support
- 19:18Why Rust for Pixie
- 21:03Supply chain security
- 24:30Pixie recap and future
- 25:56Q&A
related talks
29mExtending Python with Rust, Mojo, Cuda and C and building packages
30mConda: a cross-platform, python-agnostic binary package manager.
36mPipenv: The Future of Python Dependency Management
45mConda: a cross-platform package manager for any binary distribution
09mBuilding a Hermetic Python Environment with Conda in Bazel
24mEnsuring Runtime Reproducibility in Python
26mDependency Management in Python
39mConda-press, or Reinventing the Wheel