Re: [sage-devel] PROPOSAL: remove python3 spkg from Sage

2025-03-31 Thread Nils Bruin
On Monday, 31 March 2025 at 17:38:06 UTC-7 Trevor Karn wrote: What was the original intent behind having the dual requirements of (i) a system python and (ii) a SPKG python both in Sage? What (once upon a time) did having a SKPG do that couldn't/shouldn't/wouldn't be done by the system python?

Re: [sage-devel] Chinese Translations and Xelatex

2025-03-31 Thread Dima Pasechnik
On Mon, Mar 31, 2025 at 11:45 PM Travis Scrimshaw wrote: > > > 1. Are we allowed to have the latex engine set for xelatex and assume the > > user has this feature (if they care about compiling the pdf doc)? (The only > > other exception is uplatex for the Japanese docs.) If not, do we want to >

Re: [sage-devel] Chinese Translations and Xelatex

2025-03-31 Thread Travis Scrimshaw
> 1. Are we allowed to have the latex engine set for xelatex and assume the user has this feature (if they care about compiling the pdf doc)? (The only other exception is uplatex for the Japanese docs.) If not, do we want to make that a dependency specifically for the Chinese translation pdf

Re: [sage-devel] Chinese Translations and Xelatex

2025-03-31 Thread Dima Pasechnik
On Mon, Mar 31, 2025 at 9:48 PM Travis Scrimshaw wrote: > > Hi everyone, >There has been a PR giving a Chinese (simplified) translation of the Sage > tour: > > https://github.com/sagemath/sage/pull/39792 > > We have had a long-standing problem of getting the pdf docs to compile, but > the au

Re: [sage-devel] PROPOSAL: remove python3 spkg from Sage

2025-03-31 Thread dimpase
On Mon, Mar 31, 2025 at 07:37:23PM -0500, Trevor Karn wrote: > What was the original intent behind having the dual requirements of (i) a > system python and (ii) a SPKG python both in Sage? What (once upon a time) > did having a SKPG do that couldn't/shouldn't/wouldn't be done by the system > pytho

[sage-devel] Chinese Translations and Xelatex

2025-03-31 Thread Travis Scrimshaw
Hi everyone, There has been a PR giving a Chinese (simplified) translation of the Sage tour: https://github.com/sagemath/sage/pull/39792 We have had a long-standing problem of getting the pdf docs to compile, but the author was apparently able to solve the issue by using xelatex. However, I

Re: [sage-devel] PROPOSAL: remove python3 spkg from Sage

2025-03-31 Thread Michael Orlitzky
On 2025-03-30 14:19:21, Dima Pasechnik wrote: > I propose to remove python3 (and sqlite - which has no other consumers) > from the list of Sage spkgs (packages). > Anno 2025 one has sufficiently many non-Sage ways to make sure a good > enough python3 is available for use with Sage. This is no long

Re: [sage-devel] Re: PROPOSAL: remove python3 spkg from Sage

2025-03-31 Thread Dima Pasechnik
On 31 March 2025 14:36:30 GMT-05:00, Trevor Karn <> wrote: >If a user does not already have python3 installed on their system, this >proposal would make installing python3 a prerequisite for installing Sage >right? Is that something that we want to make users do? Well, Sage cannot be installe

Re: [sage-devel] Re: PROPOSAL: remove python3 spkg from Sage

2025-03-31 Thread Dima Pasechnik
On Mon, Mar 31, 2025 at 7:55 AM Emmanuel Charpentier wrote: > > Wouldn't that entail to have to maintain support for a wider selection of > Python versions ? Not bigger than at present. > > Le lundi 31 mars 2025 à 05:05:51 UTC+2, dim...@gmail.com a écrit : >> >> I propose to remove python3 (an

[sage-devel] Re: Proposal for GSoC 2025 – Fixing direct_product and Related Methods in Permutation Groups (Issue #34504)

2025-03-31 Thread Travis Scrimshaw
Dear Sudarshan, Thank you for your interest in GSoC. However, this mailing list is for issues related to development of Sage, not for GSoC proposal discussions. Please post such messages to the sage-gsoc list. Thank you, Travis On Monday, March 31, 2025 at 5:08:53 AM UTC+9 dandgawal...@gmail