Re: [sage-devel] Re: Another problem building Sage on 25.04

On 5/23/25 3:43 PM, Antonio Rojas wrote: Ubuntu 25.04 is shipping a broken version of m4ri, use the bundled version. Following Antonio's suggestion I tried a clean install with ./configure --with-system-m4ri=no  and everything worked perfectly. -- You received this message because you are su

[sage-devel] Re: Another problem building Sage on 25.04

Ubuntu 25.04 is shipping a broken version of m4ri, use the bundled version. El sábado, 24 de mayo de 2025 a las 0:22:46 UTC+2, richard...@gmail.com escribió: > I am unable to build sage-10.6 from source on a PC running Ubuntu > 25.04. I was able to build successfully from the same source file,

Re: [sage-devel] Re: Error building Sage on Arch

On Fri, May 23, 2025 at 11:46 AM Antonio Rojas wrote: > > Arch ships version 4.0 which builds fine with GCC 15, no patching needed. https://github.com/sagemath/sage/pull/40153 updates it to 4.0.0.0, please review > > El viernes, 23 de mayo de 2025 a las 17:38:00 UTC+2, dim...@gmail.com > escribió

Re: [sage-devel] Re: Error building Sage on Arch

Arch ships version 4.0 which builds fine with GCC 15, no patching needed. El viernes, 23 de mayo de 2025 a las 17:38:00 UTC+2, dim...@gmail.com escribió: > Hi, can we get arch's patch into Sage? > > > On May 23, 2025 3:19:22 AM CDT, Antonio Rojas wrote: > >> Install planarity from the Arch repo

Re: [sage-devel] Re: Error building Sage on Arch

Hi, can we get arch's patch into Sage? On May 23, 2025 3:19:22 AM CDT, Antonio Rojas wrote: >Install planarity from the Arch repos. The bundled version is not >compatible with GCC 15 > >El viernes, 23 de mayo de 2025 a las 9:39:36 UTC+2, benjami...@gmail.com >escribió: > >> I get and error whil

[sage-devel] Re: Error building Sage on Arch

Install planarity from the Arch repos. The bundled version is not compatible with GCC 15 El viernes, 23 de mayo de 2025 a las 9:39:36 UTC+2, benjami...@gmail.com escribió: > I get and error while compiling planarity. I attach the log file. -- You received this message because you are subscrib

[sage-devel] Re: Error building sage-10.6 on macOS Sequoia 15.5

Thank so much you all guys, Dima, Michael and Guillermo, for your prompt help. I succeeded building sage-10.7.beta3 on macOS Intel Sequoia 15.5. Best regards! Sette -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group

Re: [sage-devel] Re: should I manually adapt meson.build?

On 2025-05-16 06:38:39, 'tobia...@gmx.de' via sage-devel wrote: > You have to (pip)install `meson`. Not sure what's the sage-the-distro way > of doing this (or why meson is not automatically installed in the venv). Maybe it just needs ./sage -sh first? -- You received this message because you a

[sage-devel] Re: should I manually adapt meson.build?

You have to (pip)install `meson`. Not sure what's the sage-the-distro way of doing this (or why meson is not automatically installed in the venv). Or, preferably, after https://github.com/sagemath/sage/pull/39262 you can just run `uv run tools/update-meson.py`. On Friday, May 16, 2025 at 5:05:2

[sage-devel] Re: should I manually adapt meson.build?

Traceback (most recent call last): File "/home/martin/sage/tools/update-meson.py", line 15, in from mesonbuild.mformat import ( ModuleNotFoundError: No module named 'mesonbuild.mformat' On Friday, 16 May 2025 at 02:20:01 UTC+2 tobia...@gmx.de wrote: > Yes the meson files need to be chang

[sage-devel] Re: should I manually adapt meson.build?

Yes the meson files need to be changed whenever you add or remove python or cython files. Either run 'tools/update-meson.py' locally or apply the changes suggested in the above output manually. On Thursday, May 15, 2025 at 11:51:16 PM UTC+8 axio...@yahoo.de wrote: > The patchbot reports the fo

Re: [sage-devel] Re: dropping numpy 1 support?

Well, numpy 1 isn't going to be be supported well on Python 3.13, so that's a bit moot one way or another. I don't think Debian is working on updating their SageMath package (and Ubuntu never had its own SageMath effort, I think) We have only ourselves to blame for stalling on Debian effort. Until

[sage-devel] Re: dropping numpy 1 support?

One possible disadvantage is that Ubuntu 24.04, one of the most common distros, uses numpy 1.26 [1]. The current SageMath package for Debian/Ubuntu is 9.5, so dropping support for numpy 1 would make it impossible to release an updated the Debian/Ubuntu SageMath package. However, I don't know

Re: [sage-devel] Re: C++ Error building Sage

Hi David, I already mentioned that 10.6 release is broken. Please use the latest beta (and perhaps you will need more not yet merged patches) Dima On 1 May 2025 15:06:17 GMT-05:00, David Kohel wrote: >Hi everyone, > >Indeed, here is the relevant error line: > >../../src/sage/graphs/base/boost_i

Re: [sage-devel] Re: role of file Pipfile

That's a different Pipfile, added in a9f8401ef643 On Wed, Apr 30, 2025 at 11:48 AM 'tobia...@gmx.de' via sage-devel < sage-devel@googlegroups.com> wrote: > I'd already removed this in a merged PR > https://github.com/sagemath/sage/pull/39031. No idea why this file is now > back. Feel free to open

[sage-devel] Re: role of file Pipfile

I'd already removed this in a merged PR https://github.com/sagemath/sage/pull/39031. No idea why this file is now back. Feel free to open another PR deleting it again ;-) On Wednesday, April 30, 2025 at 8:06:39 PM UTC+8 David Coudert wrote: > I see that a file named Pipfile is generated when bu

[sage-devel] Re: Ring of integers elements inherit from FieldElement?

Ah OK, thanks. A brief look at the file makes me think it could be worked around by having a common base class NumberRingElement that can have most of the common functionality (but does NOT inherit from FieldElement) which can then be subclassed for number field elements etc. Whether maximal ord

[sage-devel] Re: Ring of integers elements inherit from FieldElement?

The inheritance from FieldElement has caused problems for a long time, and I would welcome a fix. (See issue #12242 from 2011 for example.) Please open an issue. It seems to me that the relation between OK and K should be similar to the relatio

Re: [sage-devel] Re: Devel version

ve. > > > >> Or is there something else in particular? >> >> On Thu, 24 Apr 2025 at 23:15, Dima Pasechnik wrote: >> >>> >>> >>> -- Forwarded message - >>> From: Dima Pasechnik >>> Date: Thu, Apr 24, 2

Re: [sage-devel] Re: Devel version

On Thu, Apr 24, 2025 at 4:01 PM Aram Dermenjian < aram.dermenjian.m...@gmail.com> wrote: > I ran gap and it said it's version 4.13.1, so it theoretically should be > ok? > what does this mean, exactly, you ran GAP? How? Did you run Sage's GAP, or a system-wide GAP? > > I ran the `ldd` code you

Re: [sage-devel] Re: Devel version

I ran gap and it said it's version 4.13.1, so it theoretically should be ok? I ran the `ldd` code you said, but I'm not sure how to read the output. Here's what I get: (sage-sh) aram@Cali-Alien:sd$ ldd /sage/sd/src/sage/libs/gap/ libgap.cpython-312-x86_64-linux-gnu.so linux-vdso.so.1 (0x0

Re: [sage-devel] Re: Devel version

On Thu, Apr 24, 2025 at 12:02 PM Aram Dermenjian < aram.dermenjian.m...@gmail.com> wrote: > Yeah a few times I tried doing make after and there seemed to be *some* > success sometimes. Anyway, my internet is a little more stable so it seemed > to download everything correctly. > > Now I seem to be

[sage-devel] Re: [sage-support] Sage 10.6 - Error during compilation: matplotlib/numpy incompatibility

Sage 10.6 was released with numpy 2.2.3, and matplotlib 3.8.0 from 2023, which is incompatible with numpy 2 (the compatibility was added in 3.8.4). While 10.6.rc0 was released, this problem was noticed (see https://groups.google.com/g/sage-release/c/TkPM0xL2fFA/m/LB0dT9PLAwAJ) but was not acted upo

Re: [sage-devel] Re: Devel version

Yeah a few times I tried doing make after and there seemed to be *some* success sometimes. Anyway, my internet is a little more stable so it seemed to download everything correctly. Now I seem to be getting a sagemath_doc_html error (log attached). It looks like something to do with trying to impo

Re: [sage-devel] Re: Devel version

The matplotib vs meson-python issue is pure madness, see https://github.com/sagemath/sage/pull/39789 The problem is not that one cannot build matplotlib spkg. It does work on systems we tested, and the release manager agreed. That something does not match on PyPI is not an argument. We don't use

Re: [sage-devel] Re: Devel version

You can try to restart make after you hit ctrl-C. Sometimes it just works. > Also, I'm thinking I should create a ticket along the lines of "if unable to download xxx, then an error should be thrown instead of just hanging and waiting forever", it might help to trim the list of mirrors in upstrea

Re: [sage-devel] Re: Devel version

I have run into a similar issue with the matplotlib spkg. I don't think the issue is with the download. The log file shows a few 404's but eventually the download works and the hash is correct. I think the real issue is that the matplotlib package requires a version of meson-python which is

Re: [sage-devel] Re: Devel version

On Thu, Apr 24, 2025 at 1:26 AM Aram Dermenjian < aram.dermenjian.m...@gmail.com> wrote: > Yes, that's what I'm currently trying to do, but finding all the packages > with wrong checksums is turning out to not be so fun. Have to keep > rerunning `make` to try and see which package breaks next. > >

Re: [sage-devel] Re: Devel version

Yes, that's what I'm currently trying to do, but finding all the packages with wrong checksums is turning out to not be so fun. Have to keep rerunning `make` to try and see which package breaks next. 2 questions though: 1. Is there not currently a way to do a "check integrity" run or something? Wh

Re: [sage-devel] Re: Devel version

If I am not wrong this is caused because sometimes downloading files fail. In my experience a direct download of the files, copied in the folder upstream, and restarting make is enough. El miércoles, 23 de abril de 2025 a las 19:17:15 UTC+2, aram.derme...@gmail.com escribió: > This definitely

Re: [sage-devel] Re: Devel version

This definitely solves the sci-py problem! Thanks. I'm still getting hung up on the 2nd issue though where for some reason matplotlib just won't install. The terminal goes to something like: ``` [sagenb_export-3.3] [spkg-pipinst] Installing collected packages: sagenb_export [sagenb_export-3.3] [sp

[sage-devel] Re: Devel version

Hi, This line in the scipy log: [spkg-install] g++: fatal error: Killed signal terminated program cc1plus points towards a memory issue. Could you increase the RAM devoted to WSL2 or decrease the number of processes if you are performing a parallel build (e.g use make -j4 instead of make -j8) ?

Re: [sage-devel] Re:

On Tuesday, 15 April 2025 at 08:45:53 UTC-7 Nils Bruin wrote: Note that AA was bolted onto QQbar at a later stage. Root finding over AA is currently probably implemented by root finding over QQbar and then seeing which roots lie in AA. In principle it's possible to not do it that way but I dou

Re: [sage-devel] Re:

See the documentation on QQbar . While I'm sure there are related bugs, I agree with Nils that in this case it's working as intended. If you need a very small nonzero number, the system will compute with enough precisi

Re: [sage-devel] Re:

On Tuesday, 15 April 2025 at 03:48:25 UTC-7 Georgi Guninski wrote: Just trying to show that real roots can be easily computed, not relying on the bugs in roots over QQbar. I don't see way to control the precision in the spectrum. The trick with QQbar: there IS no precision to control. The sys

Re: [sage-devel] Re:

Just trying to show that real roots can be easily computed, not relying on the bugs in roots over QQbar. I don't see way to control the precision in the spectrum. Who decides that small algebraic number is real, is it user's responsibility, discarding visual non-zero? e-60 is zero is e-58 zero or j

Re: [sage-devel] Re:

On Monday, 14 April 2025 at 10:05:20 UTC-7 Georgi Guninski wrote: I continue to think this is at least one bug. There is an easy fix via change_ring(): sage: M=F.adjacency_matrix();f=M.characteristic_polynomial();f=f.change_ring(AA) : ;ro=f.roots();sum(e for _,e in ro) 90 I'm not

Re: [sage-devel] Re:

I continue to think this is at least one bug. There is an easy fix via change_ring(): sage: M=F.adjacency_matrix();f=M.characteristic_polynomial();f=f.change_ring(AA) : ;ro=f.roots();sum(e for _,e in ro) 90 -- You received this message because you are subscribed to the Google Groups "sage-

Re: [sage-devel] Re:

On Monday, 14 April 2025 at 09:16:49 UTC-7 dim...@gmail.com wrote: One would wish there was a way to tell the system from the beginning that this particular polynomial has only real roots. Perhaps there is an easy way to implement is (a class of real-rooted polynomials), no? Dima Well, the

Re: [sage-devel] Re:

On Mon, Apr 14, 2025 at 10:58 AM Nils Bruin wrote: > > It looks like a is an element of "Qbar". Elements there are tracked by > keeping track of a way to compute a polynomial it is a root of as well as a > complex "ball" that allows one to distinguish it from other roots of the > polynomial. Ce

[sage-devel] Re:

It looks like a is an element of "Qbar". Elements there are tracked by keeping track of a way to compute a polynomial it is a root of as well as a complex "ball" that allows one to distinguish it from other roots of the polynomial. Certain operations will force the actual computation of the min

[sage-devel] Re: How do we use uv (the software)?

There is no real roadmap. The low-hanging fruit is to replace all `pip install` in CI with uv to make use of the lock file mechanism. Moreover, I could imagine the following aim for installing sage from source (without using conda): 1) Install all system packages 2) Run `uv sync` to build (and i

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

Wouldn't that entail to have to maintain support for a wider selection of Python versions ? Le lundi 31 mars 2025 à 05:05:51 UTC+2, dim...@gmail.com a écrit : > I propose to remove python3 (and sqlite - which has no other consumers) > from the list of Sage spkgs (packages). > Anno 2025 one has s

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

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? On Monday, March 31, 2025 at 9:29:27 AM UTC-5 dim...@gmail.com wrote: > On Mon, Mar 31, 2025 a

[sage-devel] Re: Problem with Using SageMath as a Python Package

We're discussing this issue here: https://github.com/sagemath/sage/issues/39740 which seems to progress forward On Friday, March 21, 2025 at 12:00:39 AM UTC-5 verner.a...@gmail.com wrote: > > Hello, > > I'm experiencing difficulties with using SageMath as a Python package. In > particular, to

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

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

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)

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

[sage-devel] Re: How to build sagelib with multiple processes in parallel?

FWIW, upgrading 6.10.beta9 to 6.10.rc0 on Debian testins ran in parallel. HTH, Le dimanche 23 mars 2025 à 19:57:40 UTC+1, Nils Bruin a écrit : > In the past I've build sagelib in parallel, with > > export MAKE="make -j8" > make -j8 build > > This seems to still work for the prerequisites, but fo

[sage-devel] Re: Error building cypari 2.2.1

Force disabling system pari for now in configure, should be fixed with https://github.com/sagemath/sage/pull/39700 El viernes, 14 de marzo de 2025 a las 2:45:37 UTC+1, Trevor Karn escribió: > Hi all, > > I'm trying to build 10.6.beta9 from source on a Apple M3 Pro running > Sequoia 15.3.1 using

[sage-devel] Re: Error building cypari 2.2.1

Thanks for the fix, Antonio. That did the trick. On Friday, March 14, 2025 at 12:37:43 AM UTC-7 Antonio Rojas wrote: > Force disabling system pari for now in configure, should be fixed with > https://github.com/sagemath/sage/pull/39700 > > El viernes, 14 de marzo de 2025 a las 2:45:37 UTC+1, Tre

[sage-devel] Re: Bug in Polyhedral complex

Thanks for the bug report. I have opened sagemath issue #39689 on github for this. On Wednesday, March 12, 2025 at 7:47:31 AM UTC-6 leif@gmail.com wrote: > Hi, > > I noticed a little bug in sage/

Re: [sage-devel] Re: WeylGroup question

Sorry for not responding earlier about this. I posted on the GH issue, but in short, you can use `W.domain().roots()` or passing it the explicit space that has the roots that you want to use, e.g., sage: W = WeylGroup(RootSystem(['G',2]).root_lattice()) sage: list(W) [ [1 0] [ 1 0] [-1 3] [

Re: [sage-devel] Re: WeylGroup question

I have opened issue #39656 for further discussion, and expect to post a comment there soon, but questions like this will probably get a better response from other forums. On Tuesday, March 4, 2025 at 5:42:38 PM UTC-7 dmo...@deductivepress.ca wrote

Re: [sage-devel] Re: WeylGroup question

Since this is related to development, you can open an issue at https://github.com/sagemath/sage/issues. If another question comes up that isn't being answered, you could ask here on sage-devel, but the answer and discussion would continue on the issue site. Anyway, I think an answer to your ori

Re: [sage-devel] Re: WeylGroup question

On Tue, Mar 4, 2025 at 11:48 AM dmo...@deductivepress.ca wrote: > > This is a question about how to use sagemath, not an issue about sagemath > development, so you should post it on a different forum, such as > ask.sagemath.org. The people there are very knowledgeable. Another option is sage-su

Re: [sage-devel] Re: WeylGroup question

Hi both, Sorry, perhaps I haven't as much detail as I should have. I am using this to develop the following package: https://github.com/Robbie-H/CompGIT/ on computing GIT quotients, which I hope it will be of use to the Sage community. I am not sure if that makes it simply an issue on how to use S

[sage-devel] Re: WeylGroup question

This is a question about how to use sagemath, not an issue about sagemath development, so you should post it on a different forum, such as ask.sagemath.org. The people there are very knowledgeable. On Tuesday, March 4, 2025 at 8:06:09 AM UTC-7 aska...@gmail.com wrote: > Hi, > > This is a long s

[sage-devel] Re: Error installing package symmetrica-3.0.1

Install the Arch symmetrica package. (And, unless you are planning to do sage development, it is highly recommended to use the sagemath distro package instead of building from source in Arch) El domingo, 2 de marzo de 2025 a las 16:23:37 UTC+1, prito...@gmail.com escribió: > Hi, > New here. Wh

[sage-devel] Re: Missing conda environment in 'src' folder

Hi Shriya, On Sunday, March 2, 2025 at 2:53:42 PM UTC+2 25sh...@gmail.com wrote: I tried creating the necessary environment - 'environment-dev-3.11-linux.yml' but there's no such environment in the source code. that file does not exist anymore on the develop branch. The documentation for the

Re: [sage-devel] Re: On plotting frac(x^2+y^2) as complex and implicit plot

I concur that it is just a moiré pattern and issues from sampling. Once you get sufficiently far from the origin, the interval of r for frac(r^2) = (0,1) gets very small (in fact, very quickly). Contrast this with f(x,y) = frac(sqrt(x^2+y^2)) It comes down to the sampling being done to make the

Re: [sage-devel] Re: On plotting frac(x^2+y^2) as complex and implicit plot

Thanks for the plots. Are you sure that the example with implicit_plot and plot_points=800 doesn't have patterns? I suspect that precision issues (float?) together with small "pixel" size incorrectly kill the pattern. implicit_plot(lambda u, v:frac(u^2+v^2)-0.5, (13, 14), (13, 14), plot_points=800

[sage-devel] Re: On plotting frac(x^2+y^2) as complex and implicit plot

I think that the shapes you perceive are moiré patterns, depending on the resolution of your plot, the resolution of your screen and the region you plot. To understand it, start with a plot of [image: \operatorname{frac}\left(x^2\right)],as done here

Re: [sage-devel] Re: RFC: demote giac to optional

Don't worry, I won't try to convince sage maintainers that they should not downgrade giac, it seems we do have too incompatible views and probably not the same target audience (which may explain that some people here believe giac is about solving a few more integrals than maxima or sympy). Howev

[sage-devel] Re: Remove one of the dancing links implementations

I have been using the c++ implementation of dancing links a lot during the last decade for fun [1,2] and for research. There were some issues in the original C++ code that are now fixed (providing a empty set of rows was crashing sage, also, we can now reset the search from the start, reduction

Re: [sage-devel] Re: Any interest in making building from source on Mac more robust?

Is your branch on the PR branch of https://github.com/sagemath/sage/pull/39571 ? It should be for the current release. I'll take the incremental testing approach. As a first set of questions: - On the Install from Source Code p

Re: [sage-devel] Re: Any interest in making building from source on Mac more robust?

Thanks, Kwankyu,, I'll take the incremental testing approach. As a first set of questions: - On the Install from Source Code page, the "macOS package installation" paragraph advises the installation of a long list of binary

Re: [sage-devel] Re: Any interest in making building from source on Mac more robust?

https://github.com/sagemath/sage/pull/39571 is needed for successful build with the latest release. On Saturday, February 22, 2025 at 10:27:40 PM UTC+9 mwi...@gmail.com wrote: Thank you, Volker, for that proof of viability of building Sage on Apple silicon (an M2 Mini) and to Kwankyu on both a

Re: [sage-devel] Re: GSoC 2025 Ideas

Hi Dima, We can still add projects. We can add projects up until the student submission deadline. However, for us to be accepted as a mentor org, we need sufficiently many new project ideas. Can you add this to the wiki page? Best, Travis On Sunday, February 23, 2025 at 8:47:12 AM UTC+9 dim.

[sage-devel] Re: Remove one of the dancing links implementations

For historical reference, both implementations were incorporated in sage in feb/march 2008: https://groups.google.com/g/sage-devel/c/COEXL3dyBS8 It looks like implementing DLX is a finnish thing :-). From the thread, I don't get the impression there is any reason to prefer the python implement

Re: [sage-devel] Re: GSoC 2025 Ideas

On Sat, Feb 22, 2025 at 09:29:35AM -0800, 'Martin R' via sage-devel wrote: > That would be awesome! Maybe it is not completely impossible to find a > suitable Lisp student, if we advertise it in the right places? well, we can add a project, still, not too late? explore and implement Python/Pyth

Re: [sage-devel] Re: GSoC 2025 Ideas

That would be awesome! Maybe it is not completely impossible to find a suitable Lisp student, if we advertise it in the right places? Martin On Thursday, 20 February 2025 at 02:56:52 UTC+1 dim...@gmail.com wrote: On 19 February 2025 09:25:12 GMT-06:00, 'Martin R' via sage-devel < sage-...@go

Re: [sage-devel] Re: Any interest in making building from source on Mac more robust?

Thank you, Volker, for that proof of viability of building Sage on Apple silicon (an M2 Mini) and to Kwankyu on both an M4 and Intel, all with macOS 15.3.1 (I assume). I would be happy to try again as suggested. But I expect I need to do some *cleaning of accumulated crud on my system* first to e

Re: [sage-devel] Re: RFC: demote giac to optional

On Fri, Feb 21, 2025 at 03:45:17PM +0100, Vincent Delecroix wrote: > I think it would be more productive to make two PRs: one for making > the package which is likely to create a consensus and one for demoting > to optional which might be controversial. The package is already done, it's in https:/

Re: [sage-devel] Re: RFC: demote giac to optional

On 2025-02-21 15:45:17, Vincent Delecroix wrote: > I think it would be more productive to make two PRs: one for making > the package which is likely to create a consensus and one for demoting > to optional which might be controversial. While generally a good idea, in this case it would create more

[sage-devel] Re: Any interest in making building from source on Mac more robust?

Ah I forgot to mention: brew upgrade and source .homebrew-build-env before "make ..." -- 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 sage-devel+unsubscr...@go

[sage-devel] Re: Any interest in making building from source on Mac more robust?

But I still want to be able to do a clean build from source on current macOS versions. Are there developers in this community with similar interests? I would be interested in collaborating with you on making the build process on macOS more robust. My main machines are all macOS. I never thou

[sage-devel] Re: Any interest in making building from source on Mac more robust?

For the record, we do have a macOS buildbot that compiles every version we release (successfully except for giac, see related thread) at http://build.sagemath.org/#/builders/16 On Friday, February 21, 2025 at 3:38:14 PM UTC+1 mwi...@gmail.com wrote: > zulipchat> > > Sage newbie. here, but long

Re: [sage-devel] Re: RFC: demote giac to optional

Giac has always segfaulted on my M2 Mac Mini buildbot, so it never got *worse* when merging a ticket. As far as I know it only works on Intel macs (endangered species as they are). For the record, +1 to making giac optional. On Friday, February 21, 2025 at 3:57:53 AM UTC+1 Dima Pasechnik wrot

Re: [sage-devel] Re: RFC: demote giac to optional

I think it would be more productive to make two PRs: one for making the package which is likely to create a consensus and one for demoting to optional which might be controversial. One important argument against optional packages is that they are rarely available in linux system pacakges (on a sys

Re: [sage-devel] Re: RFC: demote giac to optional

On Thu, Feb 20, 2025 at 1:25 PM John H Palmieri wrote: > > For what it's worth, on my macos M2 machine, giac builds but it fails its > test suite: Given that macOS is a supported platform, one has to have jolly good reasons for keeping giac standard - while it fails self-tests. If Volker would b

Re: [sage-devel] Re: A PR making changes to CI needs your attention

#39467 eliminates "minimal" CI testing: test building sage from source on platforms with minimal required system packages installed. See the relevant section on our installation guide: https://doc-release--sagemath.netlify.app/html/en/installation/source#software-prerequisites-and-recommended-p

Re: [sage-devel] Re: A PR making changes to CI needs your attention

I am for #39467 - it finally makes our CI somewhat useful and more orientated to the needs of Sage users, instead of spending KWts of electricity and lots of CPU hours on testing configurations no humans use. On 20 February 2025 05:45:08 GMT-06:00, Kwankyu Lee wrote: >I object to the PR #39467

[sage-devel] Re: RFC: demote giac to optional

For what it's worth, on my macos M2 machine, giac builds but it fails its test suite: [giac-1.9.0.15p0] [spkg-check] PASS: chk_partfrac [giac-1.9.0.15p0] [spkg-check] PASS: chk_factor [giac-1.9.0.15p0] [spkg-check] PASS: chk_integrate [giac-1.9.0.15p0] [spkg-check] PASS: chk_geo [giac-1.9.0.15p0]

[sage-devel] Re: A PR making changes to CI needs your attention

I object to the PR #39467, and prepared an alternative PR https://github.com/sagemath/sage/pull/39009 to restore the CI infrastructure to good shape. The PR #39009 is now ready for review. Please join in the discussion. -- You received this message because you are subscribed to the Google

[sage-devel] Re: Corrupted git submodule in sage repo

I remove the seemingly useless directory: subprojects/factory in the PR https://github.com/sagemath/sage/pull/39009 -- 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 t

[sage-devel] Re: RFC: demote giac to optional

Yes, by all means, please make giac optional. On Wednesday, February 19, 2025 at 5:40:03 PM UTC-6 Michael Orlitzky wrote: > Hi, I've separated sage.libs.giac into its own package, and would like > to downgrade giac to optional at the same time the new package is > added, cf. > > * https://github.

Re: [sage-devel] Re: GSoC 2025 Ideas

On 19 February 2025 09:25:12 GMT-06:00, 'Martin R' via sage-devel wrote: >I would like to remark that, as far as I know, the guessing facilities of >gfun have a reasonable replacement which is available in sage through >fricas. The last time I checked, this was more general and at least as

Re: [sage-devel] Re: GSoC 2025 Ideas

I couldn't find a way to register to this wiki, so could someone please update the page with the following info? Thanks! (Maybe for next time use https://github.com/sagemath/sage/wiki) Project: Lie group actions on manifolds Mentor: Tobias Diez, Erik? Area: Differential Geometry Skills: Knowl

Re: [sage-devel] Re: GSoC 2025 Ideas

Thanks Martin for the suggestion. I think it would be nice to improve the fricas interface as part of the project! (hint: you can help with mentoring). On Wed, 19 Feb 2025 at 16:25, 'Martin R' via sage-devel wrote: > > I would like to remark that, as far as I know, the guessing facilities of > g

Re: [sage-devel] Re: GSoC 2025 Ideas

I would like to remark that, as far as I know, the guessing facilities of gfun have a reasonable replacement which is available in sage through fricas. The last time I checked, this was more general and at least as fast than it's maple counterpart. The one thing that would dramatically improve

Re: [sage-devel] Re: GSoC 2025 Ideas

Additionally, I would like to propose that "SageMath subprojects" (such as ore_algebra, admcycles, sage-flatsurf, slabbe, ...) could make GSOC proposal under the SageMath umbrella. I believe it is easier for a newcomer to be able to contribute to a smaller standalone project. What do you thin

Re: [sage-devel] Re: GSoC 2025 Ideas

Hi Vincent^2, Thank you for the ideas and adding them to the ideas page. Best, Travis On Wednesday, February 19, 2025 at 12:18:29 AM UTC+9 Vincent Neiger wrote: > Hello, > > I just added to the wiki the two projects suggested above. Could you > please have a look to make sure I did not intro

Re: [sage-devel] Re: GSoC 2025 Ideas

Hello, I just added to the wiki the two projects suggested above. Could you please have a look to make sure I did not introduce any typo and such? In particular for the second project, as I created some title and I changed "genfun" into "gfun" which seems to be the usual name for the Maple libr

Re: [sage-devel] Re: GSoC 2025 Ideas

Additionally, I would like to propose that "SageMath subprojects" (such as ore_algebra, admcycles, sage-flatsurf, slabbe, ...) could make GSOC proposal under the SageMath umbrella. I believe it is easier for a newcomer to be able to contribute to a smaller standalone project. What do you think? On

Re: [sage-devel] Re: GSoC 2025 Ideas

I lost my wiki password but I am willing to propose to mentor on the following topics. I would welcome in anyone assisting me in the mentoring. 1) Zariski closures of finitely generated matrix groups Mentor: Vincent Delecroix + (?) Area: Algebra Skills: Group theory, Lie algebras, Number fields,

[sage-devel] Re: GSoC 2025 Ideas

Hi everyone, It would be good if people added more project ideas and/or be willing to be listed as a mentor. Google is looking more closely at what mentor orgs are putting in their ideas pages, and right now it looks like we do not have many mentors this year. It would be great to improve thi

[sage-devel] Re: Corrupted git submodule in sage repo

But there is nothing to commit! How can we fix the repo? By the way, what is this directory subprojects/factory for? Can we remove it? Removing the directory would fix the problem. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscr

[sage-devel] Re: Corrupted git submodule in sage repo

I could trace the problem to https://github.com/sagemath/sage/pull/37447 -- 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 sage-devel+unsubscr...@googlegroups.com

Re: [sage-devel] Re: Is automatic documentation from doctests a thing?

To add a generic Python explainer: generation of documentation from docstrings and function/class signatures is normally done by a Python package sphinx, and Sage is not much of an exception to it (although it's accumulated a lot of outdated "improvements" to it, which we ought to streamline as

  1   2   3   4   5   6   7   8   9   10   >