[announce] Pybi and Posy

I think some of the ideas here are interesting, though there are a few things that I’m not particularly enthused about:

  • The project is written in Rust. I personally enjoy Rust, but I think it speaks to a serious shortcoming in the idea that it relies on being written in an external language to make it viable. There’s nothing inherently Rust shaped about this project, it’s only using Rust because Rust’s packaging story can provide a workflow for projects that are targeting end user applications, instead of developer tooling.
  • The fact that everything starts from an invocation of posy means that your deployment tooling has to speak posy or it needs to give you the ability to execute an arbitrary.
  • Overall, the output of posy seems like it would be fine for hacking away at something on a developer machine, but the moment you want to deploy that code somewhere else, the model breaks down.
  • PyBI seems interesting, but it feels like the wrong direction to take things? It seems particularly silly to have two binary artifact types, one for Python things and one for Python itself. I understand that it may have been easier to just add an extra artifact type so you can just continue to support wheels, but PyBI feels like a weird hack.
  • Does the sitecustomize trick leak into virtual environments created by the posy environment? I think it will, but I’m not sure offhand.
4 Likes