This checks many of the boxes of what I have in mind as exposed here, so I am really happy to see this. I hope I manage to give it a try soon-ish, but in the mean time:
Why? I do not understand this position. It seems to me like you have all the pieces to provide a UX such as posy install 'https://github.com/httpie/httpie' so that I can use httpie without even having to think about things like how to install a Python interpreter and which one, do I need to create a virtual environment, do I need to use git or pip. httpie is a bit of a silly example because it is probably available in all package managers and installers (apt, homebrew, winget, etc.) but for something that is more niche and hard to install that could be really helpful.
But we also have the following, so I guess it is not completely out of scope:
- Python interpreters in wheels (or wheel-ish artifacts) is fantastic!
- (My wish for the future is that we have non-language-specific distribution formats so that we can
npm install pythonorposy install nodejsorpip install gccor anything like that)
- (My wish for the future is that we have non-language-specific distribution formats so that we can
- “sharing between different environments”, if it is what I think it is, then it is awesome as well
- I think I’d prefer if we had 2 tools as exposed in my post one tool to execute code for the end-user persona; and one tool to write code for the developer/redistributor/packager/etc. personas
- I think I’d prefer if this had more Python code, I see the point of using compiled code for the bootstrapping story, but maybe it could delegate to a Python interpreter (and real venvs?) as soon as possible
- Collaborate with Brett Cannon’s
python-launcher? - We need a lock file format
- Does this bring us closer to a single file distribution format for Python applications? (not installer)
Anyway, this is exciting!