As this discussion tries to wander off into a new discussion about the uv project, I will attempt to bring it back on topic.
The point is this: Currently, to build the macOS binary, we first build sage in a completely standard way. The only customization we need to do is to set up the configure options. After that completely standard build we construct the app from the sage directory. That involves removing some unneeded things, making some modifications and making Sage (not just python, *Sage*) relocatable and self-contained. But the starting point is just a completely standard build of Sage. If the Python spkg were removed we would no longer be able to start from a standard build of Sage. That first step becomes more complicated and, more importantly, non-standard. I am certain that we would be able to come up with something that works. That is not the issue. The issue is that we will have hacked the Sage build system to do that. People who are making changes that affect the Sage build system are likely to make changes which break our hack, whatever it turns out to be, because they will have no idea what the hack is and no obligation to ensure that it continues to work. With the current setup, starting from a completely standard Sage build process, there is virtually no chance that someone will break our build process for the macOS app. - Marc On Mon, Apr 7, 2025 at 8:19 AM William Stein <wst...@gmail.com> wrote: > > I believe that Homebrew wouldn't work because of the issue with rpaths > that Marc hints at earlier in his message -- in particular the paths are > baked in as /opt/homebrew/* and will not survive relocation. The "uv" > installer can install in varying locations, but I'm not sure the result is > relocatable. > > The result of using the uv installer is relocatable. (It also links > in ssl and pretty much everything, of course.) > > bash-3.2$ du -sch > > /Users/williamstein/.local/share/uv/python/cpython-3.13.2-macos-aarch64-none/* > 76K > /Users/williamstein/.local/share/uv/python/cpython-3.13.2-macos-aarch64-none/bin > 2.3M > /Users/williamstein/.local/share/uv/python/cpython-3.13.2-macos-aarch64-none/include > 45M > /Users/williamstein/.local/share/uv/python/cpython-3.13.2-macos-aarch64-none/lib > 24K > /Users/williamstein/.local/share/uv/python/cpython-3.13.2-macos-aarch64-none/share > 48M total > bash-3.2$ > /Users/williamstein/.local/share/uv/python/cpython-3.13.2-macos-aarch64-none/bin/python > Python 3.13.2 (main, Mar 17 2025, 21:26:38) [Clang 20.1.0 ] on darwin > Type "help", "copyright", "credits" or "license" for more information. > >>> > bash-3.2$ mv > /Users/williamstein/.local/share/uv/python/cpython-3.13.2-macos-aarch64-none/ > /tmp/uv-python > bash-3.2$ /tmp/uv-python/bin/python > Python 3.13.2 (main, Mar 17 2025, 21:26:38) [Clang 20.1.0 ] on darwin > Type "help", "copyright", "credits" or "license" for more information. > >>> import ssl > >>> > bash-3.2$ du -sch /tmp/uv-python > 48M /tmp/uv-python > 48M total > > The developers of uv may have put more effort into making Python easy > to distribute than we have. They want > distribution and packaging to be more modern, fast and reliable, like > it is with Rust and some other ecosystems. > > William > > > https://github.com/astral-sh/python-build-standalone > > -- > You received this message because you are subscribed to a topic in the > Google Groups "sage-devel" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/sage-devel/-ASHfAXqVYo/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > sage-devel+unsubscr...@googlegroups.com. > To view this discussion visit > https://groups.google.com/d/msgid/sage-devel/CACLE5GCqfaOgUxaQo%3DOoLPfj2YHDqYOu-0bt4UicvcBwJANbgg%40mail.gmail.com > . > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/sage-devel/CALcZXRGHme5Ufks4oBx45Voqrn5brqBjN%3D_FuiaNY%3DgYHipCZQ%40mail.gmail.com.
