[sage-devel] Re: Question about the sage venv.

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

[sage-devel] Re: Question about the sage venv.

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

[sage-devel] Re: Question about the sage venv.

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

[sage-devel] Re: Question about the sage venv.

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.

[sage-devel] Re: Question about the sage 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

[sage-devel] Re: Question about the sage venv.

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

[sage-devel] Question about the sage venv.

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? When you read PEP 405 you learn that the

[sage-devel] Ubuntu 22.04, Sage 10.3.beta0: Cannot import sage.all; caanot test due to libflint

Dear all, I have been developing on sage 10.2.rc0, i.e., the latest version prior to 10.3.beta0. I am developing on CoCalc with Ubuntu 22.04. Since some functions that I helped contribute were recently merged into 10.3.beta0, so I want to develop on this version. However, after I run `./sage

Re: [sage-devel] Re: Policy for disputed PRs: discussion

Relevant to both the overall issue of project direction *and* the specific one about Sage-as-distribution, I would just add keeping in mind the Sage mission (at least, as it currently stands): Mission: *Creating a viable free open source alternative to Magma, Maple, Mathematica and Matlab*.

Re: [sage-devel] Error installing package qepcad-B.1.72

Hi, it seems that there could be several issues at play here. First, B.1.72 dates back to from 2018, when arm64 arch wasn't very popular, and so it probably wasn't even tested. I found that Ubuntu 22 (but not Ubuntu 20) carries a version of qepad package for arm64, version B.1.74, which dates

Re: [sage-devel] Error installing sagelib-10.2 for sage-10.2 on macOS Sonoma 14.1.2

It looks like you have flint installed via Homebrew (in /usr/local), but its version is too new. Sage 10.2 still needs flint 2. Please uninstall it there and try again. Flint 3 is already in Sage 10.3.beta0, released few days ago. You might instead try using it. On Wed, Dec 6, 2023 at 10:51 PM