News for hackers. Stuff that matters.
Re:A new home for Python-build-standalone by the_mitsuhiko on Wednesday December 04, 2024 @03:24AM (#42315527)
The macOS builds in Python.org are not easy to use for tools like uv and rye. They have hardcoded paths and can only be installed to the one location on the file system. They are also framework builds which is untypical for pythons.
Re:A new home for Python-build-standalone by mkesper on Wednesday December 04, 2024 @04:49AM (#42315976)
What implies being framework builds here (-> what's the difference)?
Re:A new home for Python-build-standalone by the_mitsuhiko on Wednesday December 04, 2024 @04:55AM (#42315997)
A framework build is a specific build of Python to make it work like a .framework on macOS. The original motivation of this was that you can also ship frameworks within .app bundles but the Python framework build has hardcoded paths so you cannot really do it.

One of the consequences of framework builds is that they have a different layout than a regular Python installation on the file system. The Python installer will also litter a bunch of files into /Applications which makes installing competing versions surprisingly annoying.

In theory a framework build of Python would be preferrable but the framework build would have to become fully relocatable for that benefit to pay off. They are not today.

Re:A new home for Python-build-standalone by ameliaquining on Wednesday December 04, 2024 @07:04AM (#42316663)
And this works in macOS but not Linux because the required filesystem paths are always the same on macOS but not on Linux?
Re:A new home for Python-build-standalone by the_mitsuhiko on Thursday December 05, 2024 @03:03AM (#42326012)
It also does not work for the uv use case on Mac either.