On Thursday, December 7, 2023 at 5:04:25 PM UTC-6 Matthias Koeppe wrote:
Sure, but that would preclude using the same SAGE_LOCAL for an installation
with venv over a system python and an installation of SPKG python.
I don't understand. The bash script sage/venv/bin/sage calls
On Thursday, December 7, 2023 at 1:06:50 PM UTC-8 Marc Culler wrote:
It could stop being the case that sage/local *never* contains any python.
Instead sage/local would be the prefix for Sage's installation of Python in
the case where a system python is not being used.
Sure, but that would
On Thursday, December 7, 2023 at 2:31:24 PM UTC-6 Matthias Koeppe wrote:
> The venv would always contain a pyvenv.cfg file.
Could you explain why this matters for what you have in mind?
It is not essential. It is just cleaner and more uniform. I think it is
misleading to have something
On Thursday, December 7, 2023 at 11:06:51 AM UTC-8 Marc Culler wrote:
Would it be possible for the sage build process to use sage/local as the
unique "system location"?
The sage/local directory would be built by one stage of the sage build
process, preceding the stage that builds the venv.
Thank you, Matthias.
Now I have a followup question, which is the tip of an iceberg. The
iceberg consists of my thoughts about how to simplify and improve the
organization of files in Sage. I am not asking for a yes or no answer, or
a list of possible problems. I am just trying to find out
On Thursday, December 7, 2023 at 10:04:14 AM UTC-8 Marc Culler wrote:
I have a very narrow techical question. I am hoping for a narrow technical
answer, preferably from someone who was involved in designing the Sage venv.
QUESTION: Why doesn't the Sage venv contain a pyvenv.cfg file?
It does
