Prefix.dev - the Pixi company

Prefix.dev - the Pixi company

@prefix.dev

Escape dependency hell with Pixi - your new favorite package manager! Discord: https://discord.com/invite/kKV8ZxyzY4

254 followers15 following277 posts

You can now publish "Channel Notices" on prefix - tell your users what's new in your channel! These will be shown in the channel overview, and in Conda, Pixi and other tools.

Prefix.dev - the Pixi company reposted

Building bridges between open-source projects is a big part of why I joined @marimo.io. I got to know the @prefix.dev folks through @scipyconf.bsky.social, and worked together to make computational research easier to reproduce and share. Special thanks to @julianhofer.eu and Ruben Arts!

marimo@marimo.io

marimo now supports @prefix_dev Pixi sandboxes! Share portable notebooks with dependencies beyond Python, including CUDA-enabled @PyTorch, ffmpeg and R. Already using Conda or Pixi? Bring your ecosystem to marimo’s reactive notebooks, with Conda and PyPI requirements saved alongside your code.

The Pixi team is at ROSCON in Toronto - come find the yellow backpacks if you want to chat! We keep spotting Pixi in so many cool robotics projects and it's making us proud. To get a glimpse of what we're working on, join the talk about the EU CRA this afternoon!

Congratulations to the Mojo 1.0 release @Modular! So glad to have you in our community, and seeing @clattner_llvm on stage with `pixi` in the background was definitely a highlight for us.

[system-requirements] is deprecated. Platforms now carry the requirements themselves. CUDA and glibc constraints inline, and you can name a target what you actually call it: jetson-nano.

Simple and reproducible NVIDIA CUDA development with Pixi is easier than ever, thanks to the new capabilities of `pixi-build`. In our blogpost we build a simple kernel to run Mandelbrot on the GPU! Learn more: prefix.dev/blog/cuda-pixi

prefix.devFast, reproducible CUDA development and packaging with PixiCUDA does not need to be installed as one large system toolkit. In this post we build a terminal Mandelbrot renderer with CUDA packages from conda-forge, Pixi, and pixi-build.

More and more multi-output recipes are now building through conda-forge's new rattler-build based staging. Fast, modern, Rust-powered builds are landing in conda-forge, one recipe at a time.

Prefix.dev - the Pixi company reposted

pixi 0.76 can now run standalone python scripts in isolated, on-demand environments. dependencies live inline via PEP 723, like uv supports, but pixi can layer on conda and system dependencies too. fun to build this with @prefix.dev folks. coming to a @marimo.io notebook near you SOON.

Security tip for conda package authors: prefer environment-variable JSON files over activation scripts. Activation scripts run arbitrary shell code on every activation. Plain env-var JSON does the same job in most cases, with none of the code-execution risk.

mise, the popular dev-tool version manager, just adopted sigstore-rust, one of our open-source Rust libraries, to verify signed artifacts. Always good to see our building blocks powering other tools in the ecosystem. That is what open source is for.

Using bioconda usually means also configuring conda-forge and a few other channels by hand. Cumbersome, and easy to get wrong. Our new channel-relations CEP moves that info into repodata, so the solver just knows which channels belong together.

View full thread

Conditional dependencies (CEP 43) Deps that only apply when a condition holds. Ship one noarch package and add e.g.: pywin32[when="__win"] Conditions combine virtual packages, versions and packages with and / or / not.

Flags (CEP 45) Select build variants by named tag instead of glob-matching the build string: pytorch[flags=[gpu, blas:*]] Build with rattler-build --v3; Pixi turns v3 on automatically when it sees the new fields. Feedback welcome while it's in beta 🙏

Extras (CEP 44) Opt into optional dependency groups, just like PyPI: sqlalchemy[extras=[postgres, sqlite]] No more shipping empty sqlalchemy-postgres / -sqlite shim packages on conda-forge just to pull in the right drivers.

Increasing the security of our users and the ecosystem is a top priority for us. That's why we've added OAuth2 login flow with scoped tokens for a better `pixi auth login` experience, and scoped "Trusted Publishers" & API Keys Read more: prefix.dev/blog/pixi-a...

prefix.devA New Pixi Login FlowIncreasing the security of our users is a top priority these days. That’s why we’ve added OAuth 2.0 support to prefix.dev. You now have a fancy login-flow for Pixi and other tools.

Scoped Trusted Publishers are also actually renamed to "Repository Access" because it's not just publishing. You can give any workflow on @github or @gitlab access to pull from your private channel easily with OIDC workload identity now.