Sure. The main point is that this change is a breaking change and it was made with no general discussion and no warning. (No doubt there was some discussion in the PR, but that is not really the same thing.)
David, there is no venv directory in the source. It is a symlink created during the build process. It points to Sage's internal venv. Usually it looks something like: venv -> local/var/lib/sage/venv-python3.X.Y The file that I referred to as sage/venv/bin/sage is the main executable of sage. It could also be named sage/local/bin/sage, and I believe that it was named that before the venv was added. - Marc On Wednesday, October 1, 2025 at 11:00:13 AM UTC-5 Antonio Rojas wrote: > El miércoles, 1 de octubre de 2025 a las 17:47:02 UTC+2, David Roe > escribió: > > I'm having trouble figuring out where this change was introduced. The > folder sage/venv doesn't exist in the repo, so presumably > sage/venv/bin/sage is copied from elsewhere during the build process, but I > wasn't able to figure out where in a few minutes of poking around. > Similarly, I don't see any obvious PR descriptions in 10.8beta5 changelog > <https://github.com/sagemath/sage/releases>. > David > > > It was introduced in beta2, not beta5, so quite early in the 10.8 > development cycle. The relevant PR is > https://github.com/sagemath/sage/pull/39030. In any case, saying that > something was changed "between two beta releases" is completely meaningless > in Sage: a beta is simply a weekly development snapshot, literally every > single change is done between two beta releases. > -- 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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/sage-devel/fa36cbd2-ac07-46fe-a172-3578f7bcd163n%40googlegroups.com.
