On Wednesday, October 1, 2025 at 7:20:28 PM UTC-5 [email protected] wrote:
. Why did you assume that venv/bin/sage is what ./sage is using? You are right that I have been making some assumptions. Not that venv/bin/sage is what the so-called "./sage" is using; not even that venv/bin/sage and the so-called "./sage" are identical, even though that has been true since the venv was added. I was assuming that the venv functions as a venv and that the sage script functions as an entry point for that venv. (One of many - the venv/bin directory is quite large, and all of the scripts in it function as entry points.) They are not exactly entry points, since they are not advertised in the package metadata since there is no package metadata since there is no package (yet). And the venv has not been a "real" venv until very recently, since it did not contain a pyvenv.cfg file. But it was more or less a venv and the sage script was more or less an entry point for it, so the natural place for the sage script to live would be in the venv/bin directory. And, sure enough, there it was - right there in the venv/bin directory. It is true that there was also a copy in the top level sage directory. I assumed that was for backwards compatibility, since the venv was a relatively new addition to Sage. - Marc -- 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/d62d9938-7354-4737-9e36-0dcebf4a668an%40googlegroups.com.
