4 ms·
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 fil
by the_mitsuhiko 2y ago
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.
- mkesper 2y agoWhat implies being framework builds here (-> what's the difference)?
- the_mitsuhiko 2y agoA 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.
- ameliaquining 2y agoAnd this works in macOS but not Linux because the required filesystem paths are always the same on macOS but not on Linux?
- the_mitsuhiko 2y agoIt also does not work for the uv use case on Mac either.