11-30, 16:35–17:05 (Europe/Amsterdam), Bohr
pixi is changing the field for software environment management. pixi bridges the gap between conda and pip with a single binary tool that automatically generates lock-files and can be configured with a single configuration file. While we build on the conda ecosystem, we’re also integrating PyPi (pip) into pixi. This way you’ll only need one tool across all platforms.
Look at experiences of the current development process of most developers. Which results in why we started pixi, and why you should care about it. We’ll also dive into the differences between pixi and pip/poetry/venv.
Pixi is built in Rust, a language which you are seeing more and more often in the Python community. I’ll cover a little why we decided to use Rust and why Python developers should care about this.
Get a hands-on look at pixi and what are the features you can expect. Using some real world examples. Some robotics, some ML, some cross-platform work.
What makes package management so tricky? We’ll show some hot topics we took from PackagingCon 2023 that are interesting to Python developers like reproducibility, security and licensing. Know the issues, be part of the solution.
We're open-source. So feel free to try pixi even while I'm talking.
Resources:
- Pixi source code: https://github.com/prefix-dev/pixi
- Pixi documentation: https://prefix.dev/docs/pixi/overview
- My linkedin: https://www.linkedin.com/in/ruben-arts/
- My GitHub: https://github.com/ruben-arts
No previous knowledge expected
I studied Mechatronics/Robotics and thus started of as a robotics engineer but soon found out I get much more energy out of creating the best developer experience for my colleagues. This focus let me to switch to prefix.dev where the is my only focus for the foreseeable future.