Re: [sage-devel] Subgroups of automorphism groups of graphs

These examples reveal a bug in the commutator method --- it ignores the domain of the permutation group. I have opened .github issue #39416 for this. On Tuesday, January 28, 2025 at 3:43:56 AM UTC-7 grh...@gmail.com wrote: > It seems that this is

Re: [sage-devel] attempting to finish PR with flaky CI tests

+1 on disabling all doctests that randomly fail. https://github.com/sagemath/sage/pull/39100 might be helpful in discovering these flaky tests. Do you also want to disable CI workflows that sometimes fail for intrinsic reasons? For example, the Build & Test workflow often fails to push the tem

Re: [sage-devel] Regarding rebuilding sage

On 31 January 2025 10:39:36 GMT-06:00, Pawani Agarwal wrote: >Hello. > >make build got completed with python 3.12. I also wanted to know if I need >to run "make ptestlong". it depends upon what you need. nice to know that not many things are broken (or not...), but "make test" is testing mos

Re: [sage-devel] Regarding rebuilding sage

I am a new contributor. So I am right now exploring issues on github. So for this do I need make test? What exactly is this for Also I have already run the “make” command. On Fri, 31 Jan 2025 at 11:45 PM, Dima Pasechnik wrote: > > > On 31 January 2025 10:39:36 GMT-06:00, Pawani Agarwal < > f2021

Re: [sage-devel] Regarding rebuilding sage

Hello. make build got completed with python 3.12. I also wanted to know if I need to run "make ptestlong". Thank you for all the help. On Wed, Jan 29, 2025 at 11:58 PM Pawani Agarwal < f20212...@goa.bits-pilani.ac.in> wrote: > Okay I will try with python 3.12. make build did complete with pytho

[sage-devel] promoting hypothesis to standard spkg

At present hypothesis is optional, but it's a convenient package, used a lot together with pytest, and is a (optional?) dependency of a standard package pyrsistent The latter, strangely, lists lots of dependencies in its SPKG.rst. Anyway, the primary reason for this is that the new version of a s

Re: [sage-devel] promoting hypothesis to standard spkg

On 2025-01-31 17:38:22, Dima Pasechnik wrote: > It seems that this atrocity isn't working, as explained on > https://github.com/sagemath/sage/pull/39364 > Perhaps the reason is that hypothesis wasn't declared standard? > I'll check and report on #39364, which needs work one way or another. There's

Re: [sage-devel] attempting to finish PR with flaky CI tests

Do you also want to disable CI workflows that sometimes fail for intrinsic reasons? For example, the Build & Test workflow often fails to push the temporary Docker image that it builds (eg https://github.com/sagemath/sage/actions/runs/13036220999/job/36367766912). No. Just CI workflows that

Re: [sage-devel] Regarding rebuilding sage

On Fri, Jan 31, 2025 at 12:59 PM Pawani Agarwal wrote: > > I am a new contributor. So I am right now exploring issues on github. So for > this do I need make test? What exactly is this for 1) to check that your Sage install is OK 2) after you made changes in Sage code, to check that you didn't b

Re: [sage-devel] promoting hypothesis to standard spkg

On Fri, Jan 31, 2025 at 5:05 PM Michael Orlitzky wrote: > > On 2025-01-31 10:21:34, Dima Pasechnik wrote: > > Anyway, the primary reason for this is that the new version of a > > standard package gmpy2 uses hypothesis in its testsuite, so without it > > installed spkg-check fails for it, > > as fo

Re: [sage-devel] Patching Sage's Python's packages

On Fri, Jan 31, 2025 at 5:09 PM Gareth Ma wrote: > > Not sure how to title the subject because I am not familiar with Sage's build > system at all, but hope the body explains what it means. > > === > > Usually, I build Sage with `./bootstrap && ./configure && make build`, but I > believe t

[sage-devel] Re: Patching Sage's Python's packages

Does it help if you run "make V=0 build"? "V=0" sets the verbosity level to zero, and when I use that, I don't see any such message printed to the screen. They're still written to the log files, and I think that's good: the default should be to write with full verbosity to the log files. On Fri

[sage-devel] Patching Sage's Python's packages

Not sure how to title the subject because I am not familiar with Sage's build system at all, but hope the body explains what it means. === Usually, I build Sage with `./bootstrap && ./configure && make build`, but I believe the same problem below happens for conda install as well (the set

Re: [sage-devel] promoting hypothesis to standard spkg

On 2025-01-31 10:21:34, Dima Pasechnik wrote: > Anyway, the primary reason for this is that the new version of a > standard package gmpy2 uses hypothesis in its testsuite, so without it > installed spkg-check fails for it, > as found here: https://github.com/sagemath/sage/pull/39364 > (where I upda

[sage-devel] Re: Patching Sage's Python's packages

Also, you can tell whether Sage built Python by looking (a) at the output to the initial ./configure command, and (b) see if there is a python3-3.12.log file (or some file name like that) in logs/pkgs/. Similar for setuptools. I think the default is for Sage to build its own setuptools, even if