[sage-devel] Re: sphinx, texinfo and emacs

[Matthias Koeppe]

On Friday, October 21, 2016 at 1:18:48 PM UTC-7, John H Palmieri wrote:
>
> On Friday, October 21, 2016 at 12:31:01 PM UTC-7, Martin R wrote:
>>
>>
>> 3.) building info files requires that makeinfo is installed.  What is the 
>> proper way to deal with this?
>>
>
> Check whether it's installed in some robust way and don't build the "info" 
> output type if it's not? What other choice do we have? I don't think we 
> want an optional "makeinfo" package.
>

We already have makeinfo as part of the autotools package. 

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Troubles communicating with Sage 7.4

[Matthias Koeppe]

On Saturday, October 22, 2016 at 10:52:20 PM UTC-7, Andrey Novoseltsev 
wrote:
>
>  I have further problems (now with 7.5beta0 + #21743), sending new line 
> during installation of an experimental package (cryptominisat) is ignored 
> here:
>
> https://github.com/sagemath/sagecell/blob/master/contrib/vm/container_manager.py#L461
> The terminal got stuck on the [Y/n] question and then continued when I 
> pressed Enter myself. Any clue or solution for this one?
>

https://trac.sagemath.org/ticket/21082 

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Troubles communicating with Sage 7.4

[Matthias Koeppe]

Ticket #21082 - Prompting about experimental packages: `sage -i -y` is now 
ready for review. 

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Make xz a standard package ?

[Matthias Koeppe]

On Sunday, October 23, 2016 at 8:15:19 AM UTC-7, Emmanuel Charpentier wrote:
>
> [...] make xz a standard package. 
>

+1 

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: R 3.3.1 depends on a SSL/TLS implementation

[Matthias Koeppe]

On Friday, October 28, 2016 at 8:03:26 AM UTC-7, William wrote:
>
> we should **completely and totally remove R 
> from Sage**.  
>

We could also demote the R package to "optional" or "experimental" status.
I'd support that.
 

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: threejs as standard package

[Matthias Koeppe]

On Thursday, December 29, 2016 at 2:42:59 AM UTC-8, Volker Braun wrote:
>
> Instead of an ever-increasing list of undocumented environment variables 
> like THEBE_DIR it would be nice to get that kind of runtime data from a 
> configuration file...
>
>>
>>
Two pointers to related tickets:

https://trac.sagemath.org/ticket/21479 introduces a configuration file 
(generated by $SAGE_ROOT/configure) sage-env-config
https://trac.sagemath.org/ticket/21707 has an initial discussion on 
splitting up configuration into build-time environment variables for 
sage-the-distribution, build-time environment variables for sagelib, and 
run-time environment variables of sage.

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Release note auto-generation RFC

[Matthias Koeppe]

One could perhaps use metatickets on trac for that.

On Thursday, January 12, 2017 at 10:01:55 AM UTC-8, Volker Braun wrote:
>
> The whole point of NEWS would be to have coarser granularity than 
> individual tickets. E.g. 7.4 -> 7.5 is over 300 tickets, and a 300-item 
> list is never a good answer to the question "whats new in this release". I 
> would envision a list of, say, 10-20 highlights to have associated news 
> fragments.
>
>>

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] trouble compiling on debian sid

[Matthias Koeppe]

I haven't looked at the details, but I would guess that singular's polymake 
interface is out of date / untested (our polymake package is up to date). A 
ticket should be created and upstream singular be notified.

Matthias

On Thursday, January 12, 2017 at 11:00:36 AM UTC-8, François wrote:
>
> I now see that was indeed the problem. No easy to solve it sage side 
> without dropping the experimental polymake package or never building the 
> singular interface to it. 
> Considering version problems between singular and polymake, the later 
> would be my inclination.
>
> Francois 
>
> On 13/01/2017, at 7:51 AM, Francois Bissey  > wrote:
>
> Would you happen to have polymake installed system wide?
>
> Francois 
>
> On 13/01/2017, at 12:29 AM, moritz > 
> wrote:
>
> When trying to build sage from source on my debian box with a current sid 
> install, I get the following error:
>
> [singular-4.1.0p1] ../../../gfanlib/gfanlib_matrix.h:221:24: warning: 
> comparison between signed and unsigned integer expressions [-Wsign-compare]
> [singular-4.1.0p1] Makefile:573: recipe for target 
> 'polymake_la-polymake_conversion.lo' failed
> [singular-4.1.0p1] make[8]: *** [polymake_la-polymake_conversion.lo] Error 
> 1
>
> In the log file, I get a couple of the following errors:
> polymake_conversion.cc:176:56: error: cannot convert 
> 'pm::array_traits::iterator {aka pm::ptr_wrapper false>}' to 'const pm::Integer*' in initialization
>
> If it helps I will gladly attach the log file.
>
> The version I am trying to build is the current develop branch 7.5.rc3, 
> but I also get an error for the master branch.
>
> Any help would be highly appreciated!
>
>
> -- 
> 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+...@googlegroups.com .
> To post to this group, send email to sage...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>
> This email may be confidential and subject to legal privilege, it may
> not reflect the views of the University of Canterbury, and it is not
> guaranteed to be virus free. If you are not an intended recipient,
> please notify the sender immediately and erase all copies of the message
> and any attachments.
>
> Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
> information.
>
> -- 
> 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+...@googlegroups.com .
> To post to this group, send email to sage...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>
> This email may be confidential and subject to legal privilege, it may
> not reflect the views of the University of Canterbury, and it is not
> guaranteed to be virus free. If you are not an intended recipient,
> please notify the sender immediately and erase all copies of the message
> and any attachments.
>
> Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
> information.
>
>

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Release note auto-generation RFC

[Matthias Koeppe]

On Friday, January 13, 2017 at 11:38:50 AM UTC-8, Jori Mäntysalo wrote:
>
>
> If #1 adds foo() to graphs and #2 adds bar(), then the list should have 
> something like "Graph enchancements: foo() and bar()." Which ticket should 
> contain that information? 
>
>
Meta-ticket #3 "Graph enhancements in Sage 7.6", which depends on and 
merges #1 and #2.

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Conda package for Sage

[Matthias Koeppe]

On Sunday, February 5, 2017 at 4:27:02 AM UTC-8, Isuru Fernando wrote:
>
>
> Anybody interested in making proper conda packages for the remaining 74 
> packages and sage itself?
>

People interested in this effort may want to look at:
https://trac.sagemath.org/ticket/21507
Task ticket: Make sagelib a pip-installable Python source package, listed 
on PyPI 

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] polymake interface merged in 8.0.beta1; needs users, developers for integrating polymake features

[Matthias Koeppe]

polymake (https://polymake.org/doku.php) is an excellent, mature, and 
actively maintained open source system for interactive computations in 
polyhedral geometry (and matroids, tropical geometry, ...), developed since 
1997 by Ewgenij Gawrilow and Michael Joswig and various contributors 
(https://polymake.org/doku.php/team).

Thanks to the work by Simon King during Sage Days 84 
(https://wiki.sagemath.org/days84), there is now a pexpect-based interface 
to polymake in Sage. The spkg for polymake is also up to date, packaging 
the recently released version 3.1. Several follow-up tickets have added 
data conversion to polymake objects via polymake(x) and from polymake 
objects via x.sage(); and a backend for the Polyhedron class using 
polymake. The latter, in particular, offers fast computations for polyhedra 
over quadratic fields.

These tickets have been merged in version 8.0.beta1. 
See https://trac.sagemath.org/ticket/22710 for a meta-ticket that is 
tracking polymake-related development.

Now users and developers are needed who help to integrate polymake's 
features fully into Sage. With little effort, Sage can now become the go-to 
system for polyhedral computation (and perhaps other areas such as tropical 
geometry); on the other hand, Sage will help expand the user base of 
polymake by introducing the powerful features that polymake offers to a new 
set of users.


-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] pip install on MacOS

[Matthias Koeppe]

https://trac.sagemath.org/ticket/21944 has some work in this direction.

On Friday, May 5, 2017 at 9:35:35 AM UTC-7, Anne Schilling wrote:
>
> Hi John,
>
> Thank you, that worked!
>
> It would still be interesting to understand whether the pip/ssl problem 
> could be solved.
>
> Best wishes,
>
> Anne
>
> On Friday, May 5, 2017 at 9:23:29 AM UTC-7, John H Palmieri wrote:
>>
>> This is not a solution to the pip/ssl problem, but for a single package 
>> like snakeviz, you can go to https://pypi.python.org/pypi/snakeviz, 
>> download the tar.gz file, and then do
>>
>>   sage -pip install /path/to/snakeviz-0.4.1.tar.gz
>>
>> -- 
>> John
>>
>

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Normaliz and parallel doctest

[Matthias Koeppe]

Hi Travis, 
please try if setting OMP_NUM_THREADS=4 or smaller fixes this problem. 
This is something that I have to do in the CI scripts for Normaliz also 
(https://github.com/Normaliz/Normaliz/blob/master/.travis-build.sh#L7)
Best,
Matthias

On Saturday, May 13, 2017 at 12:45:46 PM UTC-7, Travis Scrimshaw wrote:
>
> For the combinat/rigged_configurations, I recently changed the iteration 
> method to use lattice point counting using normaliz (if installed). 
> However, when running the doctests in parallel with normaliz installed, 
> this causes a significant slowdown:
>
> travis@apricot:~/sage-build$ ./sage -tp 2 src/sage/combinat/
> rigged_configurations/*
> too many failed tests, not using stored timings
> Running doctests with ID 2017-05-13-14-41-00-970329a3.
> Git branch: public/crystals/speedup_rigged_configurations-TBA
> Using 
> --optional=coxeter3,database_gap,gambit,libbraiding,libhomfly,meataxe,mpir,normaliz,ore_algebra,pynormaliz,python2,sage,sirocco
> Sorting sources by runtime so that slower doctests are run first
> Doctesting 24 files using 2 threads.
> sage -t src/sage/combinat/rigged_configurations/kr_tableaux.py
> [238 tests, 9.41 s]
> sage -t src/sage/combinat/rigged_configurations/bij_type_B.py
> [41 tests, 5.29 s]
> sage -t 
> src/sage/combinat/rigged_configurations/rigged_configuration_element.py
> [268 tests, 17.18 s]
> sage -t 
> src/sage/combinat/rigged_configurations/tensor_product_kr_tableaux_element.py
> [75 tests, 5.61 s]
> sage -t src/sage/combinat/rigged_configurations/rigged_configurations.py
> [214 tests, 15.21 s]
> sage -t src/sage/combinat/rigged_configurations/rc_infinity.py
> [105 tests, 2.07 s]
> sage -t 
> src/sage/combinat/rigged_configurations/tensor_product_kr_tableaux.py
> [91 tests, 4.31 s]
> sage -t src/sage/combinat/rigged_configurations/bij_infinity.py
> [44 tests, 1.87 s]
> sage -t src/sage/combinat/rigged_configurations/rc_crystal.py
> [83 tests, 1.13 s]
> sage -t src/sage/combinat/rigged_configurations/bij_type_E67.py
> [68 tests, 2.95 s]
> sage -t src/sage/combinat/rigged_configurations/bij_abstract_class.py
> [66 tests, 0.77 s]
> sage -t src/sage/combinat/rigged_configurations/kleber_tree.py
> [218 tests, 37.54 s]
> sage -t src/sage/combinat/rigged_configurations/bij_type_D.py
> [79 tests, 0.77 s]
> sage -t src/sage/combinat/rigged_configurations/bij_type_D_twisted.py
> [29 tests, 0.57 s]
> sage -t src/sage/combinat/rigged_configurations/bij_type_C.py
> [28 tests, 0.54 s]
> sage -t src/sage/combinat/rigged_configurations/bij_type_A2_dual.py
> [19 tests, 0.48 s]
> sage -t src/sage/combinat/rigged_configurations/bij_type_A2_odd.py
> [19 tests, 0.49 s]
> sage -t src/sage/combinat/rigged_configurations/bij_type_D_tri.py
> [19 tests, 0.48 s]
> sage -t src/sage/combinat/rigged_configurations/bij_type_A2_even.py
> [19 tests, 0.48 s]
> sage -t src/sage/combinat/rigged_configurations/bijection.py
> [6 tests, 0.35 s]
> sage -t src/sage/combinat/rigged_configurations/rigged_partition.py
> [58 tests, 0.46 s]
> sage -t src/sage/combinat/rigged_configurations/__init__.py
> [0 tests, 0.00 s]
> sage -t src/sage/combinat/rigged_configurations/all.py
> [0 tests, 0.00 s]
> sage -t src/sage/combinat/rigged_configurations/bij_type_A.py
> [19 tests, 0.36 s]
> --
> All tests passed!
> --
> Total time for all tests: 54.9 seconds
> cpu time: 367.9 seconds
> cumulative wall time: 108.3 seconds
>
>
>
> Compare when run in series:
>
> travis@apricot:~/sage-build$ ./sage -t src/sage/combinat/
> rigged_configurations/*
> too many failed tests, not using stored timings
> Running doctests with ID 2017-05-13-14-39-54-6e47b138.
> Git branch: public/crystals/speedup_rigged_configurations-TBA
> Using 
> --optional=coxeter3,database_gap,gambit,libbraiding,libhomfly,meataxe,mpir,normaliz,ore_algebra,pynormaliz,python2,sage,sirocco
> Doctesting 24 files.
> sage -t src/sage/combinat/rigged_configurations/all.py
> [0 tests, 0.00 s]
> sage -t src/sage/combinat/rigged_configurations/bij_abstract_class.py
> [66 tests, 0.56 s]
> sage -t src/sage/combinat/rigged_configurations/bijection.py
> [6 tests, 0.33 s]
> sage -t src/sage/combinat/rigged_configurations/bij_infinity.py
> [44 tests, 0.70 s]
> sage -t src/sage/combinat/rigged_configurations/bij_type_A2_dual.py
> [19 tests, 0.43 s]
> sage -t src/sage/combinat/rigged_configurations/bij_type_A2_even.py
> [19 tests, 0.42 s]
> sage -t src/sage/combinat/rigged_configurations/bij_type_A2_odd.py
> [19 tests, 0.43 s]
> sage -t src/sage/combinat/rigged_configurations/bij_type_A.py
> [19 tests, 0.32 s]
> sage -t src/sage/combinat/rigged_configurations/bij_type_B.py
> [41 tests, 1.85 s]
> sage -t src/sage/combinat/rigged_configurations/bij_type_C.py
> [28 tests, 0.46 s]
> sage -

Re: [sage-devel] Re: Normaliz and parallel doctest

[Matthias Koeppe]

I suppose one could try to set this using os.putenv in the doctests.

On Tue, May 16, 2017 at 2:41 PM, Travis Scrimshaw  wrote:
> Hey Matthias,
>Yes, that fixes the problem. Thank you.
>
> The next question is do we want to (temporarily) set this to, say, 1 when
> running the doctests? If so, then how/where?
>
> Best,
> Travis
>
>
>
> On Tuesday, May 16, 2017 at 12:29:51 PM UTC-5, Matthias Koeppe wrote:
>>
>> Hi Travis,
>> please try if setting OMP_NUM_THREADS=4 or smaller fixes this problem.
>> This is something that I have to do in the CI scripts for Normaliz also
>> (https://github.com/Normaliz/Normaliz/blob/master/.travis-build.sh#L7)
>> Best,
>> Matthias
>>
>> On Saturday, May 13, 2017 at 12:45:46 PM UTC-7, Travis Scrimshaw wrote:
>>>
>>> For the combinat/rigged_configurations, I recently changed the iteration
>>> method to use lattice point counting using normaliz (if installed). However,
>>> when running the doctests in parallel with normaliz installed, this causes a
>>> significant slowdown:
>>>
>>> travis@apricot:~/sage-build$ ./sage -tp 2
>>> src/sage/combinat/rigged_configurations/*
>>> too many failed tests, not using stored timings
>>> Running doctests with ID 2017-05-13-14-41-00-970329a3.
>>> Git branch: public/crystals/speedup_rigged_configurations-TBA
>>> Using
>>> --optional=coxeter3,database_gap,gambit,libbraiding,libhomfly,meataxe,mpir,normaliz,ore_algebra,pynormaliz,python2,sage,sirocco
>>> Sorting sources by runtime so that slower doctests are run first
>>> Doctesting 24 files using 2 threads.
>>> sage -t src/sage/combinat/rigged_configurations/kr_tableaux.py
>>> [238 tests, 9.41 s]
>>> sage -t src/sage/combinat/rigged_configurations/bij_type_B.py
>>> [41 tests, 5.29 s]
>>> sage -t
>>> src/sage/combinat/rigged_configurations/rigged_configuration_element.py
>>> [268 tests, 17.18 s]
>>> sage -t
>>> src/sage/combinat/rigged_configurations/tensor_product_kr_tableaux_element.py
>>> [75 tests, 5.61 s]
>>> sage -t src/sage/combinat/rigged_configurations/rigged_configurations.py
>>> [214 tests, 15.21 s]
>>> sage -t src/sage/combinat/rigged_configurations/rc_infinity.py
>>> [105 tests, 2.07 s]
>>> sage -t
>>> src/sage/combinat/rigged_configurations/tensor_product_kr_tableaux.py
>>> [91 tests, 4.31 s]
>>> sage -t src/sage/combinat/rigged_configurations/bij_infinity.py
>>> [44 tests, 1.87 s]
>>> sage -t src/sage/combinat/rigged_configurations/rc_crystal.py
>>> [83 tests, 1.13 s]
>>> sage -t src/sage/combinat/rigged_configurations/bij_type_E67.py
>>> [68 tests, 2.95 s]
>>> sage -t src/sage/combinat/rigged_configurations/bij_abstract_class.py
>>> [66 tests, 0.77 s]
>>> sage -t src/sage/combinat/rigged_configurations/kleber_tree.py
>>> [218 tests, 37.54 s]
>>> sage -t src/sage/combinat/rigged_configurations/bij_type_D.py
>>> [79 tests, 0.77 s]
>>> sage -t src/sage/combinat/rigged_configurations/bij_type_D_twisted.py
>>> [29 tests, 0.57 s]
>>> sage -t src/sage/combinat/rigged_configurations/bij_type_C.py
>>> [28 tests, 0.54 s]
>>> sage -t src/sage/combinat/rigged_configurations/bij_type_A2_dual.py
>>> [19 tests, 0.48 s]
>>> sage -t src/sage/combinat/rigged_configurations/bij_type_A2_odd.py
>>> [19 tests, 0.49 s]
>>> sage -t src/sage/combinat/rigged_configurations/bij_type_D_tri.py
>>> [19 tests, 0.48 s]
>>> sage -t src/sage/combinat/rigged_configurations/bij_type_A2_even.py
>>> [19 tests, 0.48 s]
>>> sage -t src/sage/combinat/rigged_configurations/bijection.py
>>> [6 tests, 0.35 s]
>>> sage -t src/sage/combinat/rigged_configurations/rigged_partition.py
>>> [58 tests, 0.46 s]
>>> sage -t src/sage/combinat/rigged_configurations/__init__.py
>>> [0 tests, 0.00 s]
>>> sage -t src/sage/combinat/rigged_configurations/all.py
>>> [0 tests, 0.00 s]
>>> sage -t src/sage/combinat/rigged_configurations/bij_type_A.py
>>> [19 tests, 0.36 s]
>>> --
>>> All tests passed!
>>> --
>>> Total time for all tests: 54.9 seconds
>>> cpu time: 367.9 seconds
>>> cumulative wall time: 108.3 seconds
>>>
>>>
>>>
>>&g

Re: [sage-devel] Re: Normaliz and parallel doctest

[Matthias Koeppe]

I think it is really an upstream problem with normaliz. We could try
to work around it in our normaliz interface (not just the doctest)
because it may also affect computation time in general on some
hardware. (I never ran into trouble with it on my machine.)

On Wed, May 17, 2017 at 5:24 PM, Travis Scrimshaw  wrote:
> Well, we could do something in each doctest, but this is cumbersome and ugly
> IMO. I was thinking of something more in the doctesting framework.
>
> Best,
> Travis
>
>
> On Wednesday, May 17, 2017 at 6:38:51 PM UTC-5, Matthias Koeppe wrote:
>>
>> I suppose one could try to set this using os.putenv in the doctests.
>>
>> On Tue, May 16, 2017 at 2:41 PM, Travis Scrimshaw 
>> wrote:
>> > Hey Matthias,
>> >Yes, that fixes the problem. Thank you.
>> >
>> > The next question is do we want to (temporarily) set this to, say, 1
>> > when
>> > running the doctests? If so, then how/where?
>> >
>> > Best,
>> > Travis
>> >
>> >
>> >
>> > On Tuesday, May 16, 2017 at 12:29:51 PM UTC-5, Matthias Koeppe wrote:
>> >>
>> >> Hi Travis,
>> >> please try if setting OMP_NUM_THREADS=4 or smaller fixes this problem.
>> >> This is something that I have to do in the CI scripts for Normaliz also
>> >> (https://github.com/Normaliz/Normaliz/blob/master/.travis-build.sh#L7)
>> >> Best,
>> >> Matthias
>> >>
>> >> On Saturday, May 13, 2017 at 12:45:46 PM UTC-7, Travis Scrimshaw wrote:
>> >>>
>> >>> For the combinat/rigged_configurations, I recently changed the
>> >>> iteration
>> >>> method to use lattice point counting using normaliz (if installed).
>> >>> However,
>> >>> when running the doctests in parallel with normaliz installed, this
>> >>> causes a
>> >>> significant slowdown:
>> >>>
>> >>> travis@apricot:~/sage-build$ ./sage -tp 2
>> >>> src/sage/combinat/rigged_configurations/*
>> >>> too many failed tests, not using stored timings
>> >>> Running doctests with ID 2017-05-13-14-41-00-970329a3.
>> >>> Git branch: public/crystals/speedup_rigged_configurations-TBA
>> >>> Using
>> >>>
>> >>> --optional=coxeter3,database_gap,gambit,libbraiding,libhomfly,meataxe,mpir,normaliz,ore_algebra,pynormaliz,python2,sage,sirocco
>> >>> Sorting sources by runtime so that slower doctests are run first
>> >>> Doctesting 24 files using 2 threads.
>> >>> sage -t src/sage/combinat/rigged_configurations/kr_tableaux.py
>> >>> [238 tests, 9.41 s]
>> >>> sage -t src/sage/combinat/rigged_configurations/bij_type_B.py
>> >>> [41 tests, 5.29 s]
>> >>> sage -t
>> >>>
>> >>> src/sage/combinat/rigged_configurations/rigged_configuration_element.py
>> >>> [268 tests, 17.18 s]
>> >>> sage -t
>> >>>
>> >>> src/sage/combinat/rigged_configurations/tensor_product_kr_tableaux_element.py
>> >>> [75 tests, 5.61 s]
>> >>> sage -t
>> >>> src/sage/combinat/rigged_configurations/rigged_configurations.py
>> >>> [214 tests, 15.21 s]
>> >>> sage -t src/sage/combinat/rigged_configurations/rc_infinity.py
>> >>> [105 tests, 2.07 s]
>> >>> sage -t
>> >>> src/sage/combinat/rigged_configurations/tensor_product_kr_tableaux.py
>> >>> [91 tests, 4.31 s]
>> >>> sage -t src/sage/combinat/rigged_configurations/bij_infinity.py
>> >>> [44 tests, 1.87 s]
>> >>> sage -t src/sage/combinat/rigged_configurations/rc_crystal.py
>> >>> [83 tests, 1.13 s]
>> >>> sage -t src/sage/combinat/rigged_configurations/bij_type_E67.py
>> >>> [68 tests, 2.95 s]
>> >>> sage -t src/sage/combinat/rigged_configurations/bij_abstract_class.py
>> >>> [66 tests, 0.77 s]
>> >>> sage -t src/sage/combinat/rigged_configurations/kleber_tree.py
>> >>> [218 tests, 37.54 s]
>> >>> sage -t src/sage/combinat/rigged_configurations/bij_type_D.py
>> >>> [79 tests, 0.77 s]
>> >>> sage -t src/sage/combinat/rigged_configurations/bij_type_D_twisted.py
>> >>> [29 tests, 0.57 s]
>> >>> sage -t src/sage/combinat/rigged_configurations/bij_type_C.py
>> >>> [28 tests, 0.54 s]

Re: [sage-devel] Sage Python 3 proposal

[Matthias Koeppe]

On Friday, June 2, 2017 at 2:01:25 AM UTC-7, François wrote:
>
>
> Actually there has been some work on enabling sage to be built and 
> installed in a prefix that isn’t under SAGE_ROOT. This is why we now 
> have sage-env-config. 
> So you could do a run of configure of sage with python2 and install it 
> in $prefix_python2 and then do the same for python3 but install it 
> in $prefix_python3. Out of the same source tree. 
> Some cleaning may be required between builds, I haven’t actually worked 
> on the functionality myself. 
>
>
In addition to the recently implemented feature `./configure --prefix=...` 
that you mention above, we would also need out-of-tree builds (VPATH 
builds); this is the standard autotools mechanism for having several build 
configurations from one source tree. (No cleaning in between builds will be 
required with this method; the source tree is always clean.) There is 
initial work in this direction on this ticket: 
https://trac.sagemath.org/ticket/21469 (it needs rebasing and updating).


-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: copying MixedIntegerLinearProgram problem

[Matthias Koeppe]

Please see http://trac.sagemath.org/ticket/20461
Comments welcome.

On Thu, May 12, 2016 at 1:02 AM, Dima Pasechnik  wrote:
> Hi,
> Matthias Koeppe did a lot of work on MILPs recently, in particular on
> copying LPs, see e.g.
> http://trac.sagemath.org/ticket/20414
> and the meta-ticket http://trac.sagemath.org/ticket/20302
> Not sure whether he reads this, I cc to him.
> I presume you got one of these updates messing up your code.
> Dima
>
>
>
> On Thursday, May 12, 2016 at 8:18:07 AM UTC+1, Martin R wrote:
>>
>> Hi there!
>>
>> I am having a severe problem with a program of mine that stopped working,
>> very likely after upgrading to 7.2.beta5, but I'm afraid I don't know from
>> which version.  (I believe something after 7.1)
>>
>> The error I get is:
>>
>> ValueError: Variable MIPVariable of dimension 1 is a variable from a
>> different problem
>>
>> What I want to do is: check whether a MILP has a solution, and if so,
>> check whether it still has a solution if I add a further constraint.  The
>> MILP's take a very long time to solve.
>>
>> What I do and what worked until very recently is roughly:
>>
>> p = MixedIntegerLinearProgram(constraint_generation=True,
>> solver="CPLEX") # solver="GLPK") # twice as long #
>> assignment = p.new_variable(binary=True)
>>
>> p.add_constraint(... some relations in terms of assignment[box,
>> colour] ... )
>>
>> p.solve()
>>
>> for (box, colour) in large_list:
>> p_new = copy(p)
>> p_new.add_constraint(assignment[box, colour] == 0)
>> try:
>> p_new.solve()
>>
>> bang!
>>
>> What should I do?
>>
>> I don't have a minimal example exhibiting the error, but if absolutely
>> needed, I'd try to create one.
>>
>> Many thanks,
>>
>> Martin



-- 
Matthias Koeppe -- http://www.math.ucdavis.edu/~mkoeppe

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Polyhedron.integral_points_count() gives inconsistent answers on slices

[Matthias Koeppe]

On Friday, November 3, 2017 at 1:41:33 PM UTC-7, Mark Bell wrote:
>
> So when k = 19, sage.interfaces.latte.count 
> 
>  
> and P.integral_points_count() give different answers. This seems to be the 
> cause of the difference. Here is some more code showing the difference.
>

The bug appears to be in the preprocessing code of integral_points_count().
If you use preprocess=False, the number of lattice points is correct (19).

 

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Polyhedron.integral_points_count() gives inconsistent answers on slices

[Matthias Koeppe]

On Friday, November 3, 2017 at 5:06:13 PM UTC-7, Matthias Koeppe wrote:
>
> On Friday, November 3, 2017 at 1:41:33 PM UTC-7, Mark Bell wrote:
>>
>> So when k = 19, sage.interfaces.latte.count 
>> <http://doc.sagemath.org/html/en/reference/interfaces/sage/interfaces/latte.html>
>>  
>> and P.integral_points_count() give different answers. This seems to be the 
>> cause of the difference. Here is some more code showing the difference.
>>
>
> The bug appears to be in the preprocessing code of integral_points_count().
> If you use preprocess=False, the number of lattice points is correct (19).
>
> Looks like to_linear_program() handles equations wrong!
 

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Polyhedron.integral_points_count() gives inconsistent answers on slices

[Matthias Koeppe]

On Friday, November 3, 2017 at 5:22:16 PM UTC-7, Matthias Koeppe wrote:
>
> On Friday, November 3, 2017 at 5:06:13 PM UTC-7, Matthias Koeppe wrote:
>>
>> On Friday, November 3, 2017 at 1:41:33 PM UTC-7, Mark Bell wrote:
>>>
>>> So when k = 19, sage.interfaces.latte.count 
>>> <http://doc.sagemath.org/html/en/reference/interfaces/sage/interfaces/latte.html>
>>>  
>>> and P.integral_points_count() give different answers. This seems to be the 
>>> cause of the difference. Here is some more code showing the difference.
>>>
>>
>> The bug appears to be in the preprocessing code of 
>> integral_points_count().
>> If you use preprocess=False, the number of lattice points is correct (19).
>>
>> Looks like to_linear_program() handles equations wrong!
>

Ticket at https://trac.sagemath.org/ticket/24154 

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Polyhedron.integral_points_count() gives inconsistent answers on slices

[Matthias Koeppe]

On Friday, November 3, 2017 at 5:44:43 PM UTC-7, Matthias Koeppe wrote:
>
> On Friday, November 3, 2017 at 5:22:16 PM UTC-7, Matthias Koeppe wrote:
>>
>> On Friday, November 3, 2017 at 5:06:13 PM UTC-7, Matthias Koeppe wrote:
>>>
>>> On Friday, November 3, 2017 at 1:41:33 PM UTC-7, Mark Bell wrote:
>>>>
>>>> So when k = 19, sage.interfaces.latte.count 
>>>> <http://doc.sagemath.org/html/en/reference/interfaces/sage/interfaces/latte.html>
>>>>  
>>>> and P.integral_points_count() give different answers. This seems to be the 
>>>> cause of the difference. Here is some more code showing the difference.
>>>>
>>>
>>> The bug appears to be in the preprocessing code of 
>>> integral_points_count().
>>> If you use preprocess=False, the number of lattice points is correct 
>>> (19).
>>>
>>> Looks like to_linear_program() handles equations wrong!
>>
>
> Ticket at https://trac.sagemath.org/ticket/24154 
>

Ticket needs review. 

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Polyhedron.integral_points_count() gives inconsistent answers on slices

[Matthias Koeppe]

Can you show the output of the crash on CoCalc?

On Saturday, November 4, 2017 at 3:46:01 PM UTC-7, Mark Bell wrote:
>
> Thanks! 
>
> I'm not sure if this is the right place to add this but the attached 
> example also causes LattE to crash, but I only see this behaviour when I 
> run this code on CoCalc. When I run the script on my local machine with 
> latte_int installed it completes and prints out 19958. Surely this isn't 
> being caused by the same bug.
>

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Polyhedron.integral_points_count() gives inconsistent answers on slices

[Matthias Koeppe]

I can't reproduce this locally, but you could see if passing  

--triangulation=cddlib

to LattE helps. 

On Sunday, November 5, 2017 at 1:46:30 AM UTC-8, Mark Bell wrote:
>
> Here is the full CoCalc output when I run "sage error.py" in a terminal, 
> either via the web interface or via sshing into the machine:
>
> Traceback (most recent call last):
>   File "error.py", line 42, in 
> print(P.integral_points_count(preprocess=False))
>   File 
> "/ext/sage/sage-8.0/local/lib/python2.7/site-packages/sage/geometry/polyhedron/base_QQ.py",
>  
> line 218, in integral_points_count
> **kwds)
>   File 
> "/ext/sage/sage-8.0/local/lib/python2.7/site-packages/sage/interfaces/latte.py",
>  
> line 159, in count
> raise RuntimeError("LattE integrale program failed (exit code 
> {})".format(ret_code) + err.strip())
> RuntimeError: LattE integrale program failed (exit code -6):
> This is LattE integrale 1.7.3
> Available from http://www.math.ucdavis.edu/~latte/
>  
> Invocation: count '--redundancy-check=none' --cdd /dev/stdin
> Warning: Not performing check for empty polytope, because it is 
> unimplemented for the CDD-style input format.
> size = 22 x 19
> Number Type = rational
> Ax <= b, given as (b|-A):
> =
> [-1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]
> [-1 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]
> [-1 1 0 1 -1 0 0 0 0 0 0 0 0 0 0 0 0 0 0]
> [-1 0 1 -1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0]
> [-1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]
> [-1 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0]
> [97 -2 -8 -1 -7 0 0 0 0 0 0 0 0 0 0 0 0 0 0]
> [-1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0]
> [97 -2 -5 -1 -4 0 -3 0 0 0 0 0 0 0 0 0 0 0 0]
>
> Ax = b, given as (b|-A):
> 
> [0 1 0 1 -1 0 0 0 0 0 0 0 0 0 0 0 0 0 -1]
> [0 0 1 -1 1 0 0 0 0 0 0 0 0 0 0 0 0 -1 0]
> [0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0]
> [0 0 1 -1 2 0 0 0 0 0 0 0 0 0 0 -1 0 0 0]
> [0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0]
> [0 0 0 0 0 0 1 0 0 0 0 0 0 -1 0 0 0 0 0]
> [-100 2 8 1 7 0 0 0 0 0 0 0 3 0 0 0 0 0 0]
> [0 0 1 0 1 0 0 0 0 0 0 -1 0 0 0 0 0 0 0]
> [0 0 1 0 1 0 0 0 0 0 -1 0 0 0 0 0 0 0 0]
> [0 0 1 1 0 0 0 0 0 -1 0 0 0 0 0 0 0 0 0]
> [-100 2 5 1 4 0 3 0 3 0 0 0 0 0 0 0 0 0 0]
> [-100 2 5 1 4 0 3 3 0 0 0 0 0 0 0 0 0 0 0]
> [0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0]
>
> Computing hermitean normal form.
> sol:
> [0 0 0 0 0 0 -100 0 0 -100 0 0 0 0 0 0 0 0]
> Particular solution:
> Basis:
> New inequalities:
> [99 -3 -3 -5 -5 -1 0]
> [-101 3 3 5 6 2 0]
> [-1 0 0 0 0 1 0]
> [-1 0 0 0 1 0 0]
> [-1 0 0 1 0 0 0]
> [-1 1 0 0 0 0 0]
> [-3 3 3 -3 -3 0 0]
> [99 -3 -3 -4 -5 -2 0]
> [-3 0 3 0 0 0 0]
> Time for reading and preprocessing: 0 sec
> The polytope has 12 vertices.
> Time for computing vertices and supporting cones: 0 sec
> Time for dualizing general cones: 0 sec
> Dualizing all cones...All cones are now dualized.
> Time for dualizing general cones: 0 sec
> decomposeCones_Single: Decomposing all cones. (Memory Save on)
> 12 cones total to be done!decomposeCones_Single: degree = 1
> Number of cones: 12
> Triangulating cone... done.
> count: barvinok/barvinok.cpp:572: int 
> barvinokDecomposition_Single(listCone*, Single_Cone_Parameters*): Assertion 
> `num_rays == Parameters->Number_of_Variables'
> failed.
>

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: gambit does not build (sage 8.2.beta6)

[Matthias Koeppe]

See https://trac.sagemath.org/ticket/21864

On Wednesday, February 21, 2018 at 4:41:10 AM UTC-8, Jeroen Demeyer wrote:
>
> If somebody wants to fix this, you should try pip. gambit is currently 
> one of the few Python packages that are installed using the classical 
> setup.py script instead of pip. 
>
> Changing to pip is an obvious thing to do anyway and it might even fix 
> the problem. 
>

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Problem of reduction of rational functions

[Matthias Koeppe]

This is discussed in https://trac.sagemath.org/ticket/16993 

On Sunday, April 15, 2018 at 9:39:36 PM UTC+2, dhr wrote:
>
> Hi
>
> Reduction of rational functions seems not to work in specific cases.
> In the following output,
>
> ===
> sage: R.=QQ[]
> sage: (2*t+2)/(2*t)
> (2*t + 2)/(2*t)
> sage: (2*t+2)/(2)
> t + 1
> sage: (2*t^2+2*t)/(2*t)
> t + 1
>
> ===
> 2 is not reduced in the first calculation.
>
> SageMath version 8.1
>
>

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: python3 status

[Matthias Koeppe]

On Wednesday, May 30, 2018 at 9:01:59 AM UTC-7, Nils Bruin wrote:
>
>
> Currently, if I run the script $SAGE_LOCAL/bin/sage in my normal 
> environment (where SAGE_ROOT is not set) then I get:
>
> Error: You must set the SAGE_ROOT environment variable or run this
> script from the SAGE_ROOT or SAGE_ROOT/local/bin/ directory.
> Error setting environment variables by sourcing 
> '/usr/local/sage/sage-git/local/bin/sage-env';
> possibly contact sage-devel (see http://groups.google.com/group/sage-devel
> ).
>
> If instead I run the script $SAGE_ROOT/sage a value for SAGE_ROOT is 
> figured out and everything works fine when called from my normal 
> environment.
>
>
I agree that we should make $SAGE_LOCAL/bin/sage work without environment 
variables set.
We discussed this in https://trac.sagemath.org/ticket/21479 ("./configure 
--prefix=SAGE_LOCAL"), when $SAGE_LOCAL/bin/sage-env-config was introduced; 
but then a less ambitious solution was implemented for that ticket.

We could add a line setting $SAGE_ROOT in $SAGE_LOCAL/bin/sage-env-config 
(via src/bin/sage-env-config.in).

On the other hand, of course, most uses of SAGE_ROOT have been eliminated 
(see https://trac.sagemath.org/ticket/21591 - Replace use of SAGE_ROOT by 
more specific environment variables); and it would be good to finish this 
job and allow sage to work without having to complain about this 
environment variable.




-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: python3 status

[Matthias Koeppe]

I have created https://trac.sagemath.org/ticket/25486 for this.

On Wednesday, May 30, 2018 at 10:32:42 AM UTC-7, Matthias Koeppe wrote:
>
> On Wednesday, May 30, 2018 at 9:01:59 AM UTC-7, Nils Bruin wrote:
>>
>>
>> Currently, if I run the script $SAGE_LOCAL/bin/sage in my normal 
>> environment (where SAGE_ROOT is not set) then I get:
>>
>> Error: You must set the SAGE_ROOT environment variable or run this
>> script from the SAGE_ROOT or SAGE_ROOT/local/bin/ directory.
>> Error setting environment variables by sourcing 
>> '/usr/local/sage/sage-git/local/bin/sage-env';
>> possibly contact sage-devel (see 
>> http://groups.google.com/group/sage-devel).
>>
>> If instead I run the script $SAGE_ROOT/sage a value for SAGE_ROOT is 
>> figured out and everything works fine when called from my normal 
>> environment.
>>
>>
> I agree that we should make $SAGE_LOCAL/bin/sage work without environment 
> variables set.
> We discussed this in https://trac.sagemath.org/ticket/21479 ("./configure 
> --prefix=SAGE_LOCAL"), when $SAGE_LOCAL/bin/sage-env-config was introduced; 
> but then a less ambitious solution was implemented for that ticket.
>
> We could add a line setting $SAGE_ROOT in $SAGE_LOCAL/bin/sage-env-config 
> (via src/bin/sage-env-config.in).
>
> On the other hand, of course, most uses of SAGE_ROOT have been eliminated 
> (see https://trac.sagemath.org/ticket/21591 - Replace use of SAGE_ROOT by 
> more specific environment variables); and it would be good to finish this 
> job and allow sage to work without having to complain about this 
> environment variable.
>
>
>
>
>

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Patching policy

[Matthias Koeppe]

See 
also 
http://doc.sagemath.org/html/en/developer/packaging.html#how-to-maintain-a-set-of-patches

On Friday, June 8, 2018 at 4:05:47 AM UTC-7, Dima Pasechnik wrote:
>
>
>
> On Friday, June 8, 2018 at 9:25:33 AM UTC+1, Jeroen Demeyer wrote:
>>
>> On 2018-06-08 07:47, Ralf Stephan wrote: 
>> > It might be an idea to semi-automatize this, i.e., build a tool that 
>> > takes a Sage version and creates forks of some packages A,B on github 
>> > under sage/sage-A, sage/sage-B. 
>>
>> Which problem would that solve? 
>>
>> patches are not the best way to update things. VCSs are much better... 
>

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Announce: IMA workshop "COIN fORgery" (open source mathematical optimization tools), Oct 15-19, 2018

[Matthias Koeppe]

This workshop may be of interest to those who are working on features 
related to mathematical optimization in Sage. 

"COIN fORgery: Developing Open Source Tools for Operations Research" will 
be held at the IMA (Institute for Mathematics and its Applications, 
University of Minnesota) October 15 - 19, 2018. Similar to last year's Sage 
activities at the IMA, this workshop will be the opening workshop for a 
year of coding sprints held at the IMA.

The workshop and year-long activities center around the COIN-OR suite. One 
focus is Python interfacing; this could be most relevant for Sage 
developers. 

More info, including a draft program and a link to the IMA program 
application are available here:
https://www.coin-or.org/ima/oct2018/


-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Deprecate and remove/relocate explain_pickle module?

[Matthias Koeppe]

+1 on splitting it out as a standalone Python package. With a bit of luck, 
a new set of contributors for it can be found that way. 

On Friday, September 21, 2018 at 11:06:47 AM UTC-4, Erik Bray wrote:
>
> On Fri, Sep 21, 2018 at 4:29 PM Nils Bruin > 
> wrote: 
> > 
> > On Friday, September 21, 2018 at 1:46:47 AM UTC-7, Erik Bray wrote: 
> >> 
> >> There is a cool module in sage called sage.misc.explain_pickle, which 
> >> is useful for helping to understand and debug how non-trivial objects 
> >> in Sage are pickled and unpickled. 
> >> 
> > I am adding another testimonial  on the usefulness of the routine. On 
> several occasions I was in a pickle (sorry for the pun), which could be 
> solved immediately by explain_pickle. it was a big time-saver that it was 
> available *right there*, because I wasn't looking forward to having to hunt 
> down a third party package that may or may not help me. I also think that 
> with multiprocessing, serialization remains very important to support for 
> (hopefully) all data structures in sage. That means that whenever a new 
> structure pops up, errors and debugging will be inevitable. The problems in 
> serialization are often triggered by non-local interactions, so I would not 
> expect that problems with serialization in sage will become rarer (in fact, 
> I expect them to become more complex due to more intricate interactions). 
> > 
> > I would be a little sad to see explain_pickle go. 
>
> Per my reply to Jeroen, what if it were still "there" in 
> sage.misc.explain_pickle, but the meat of it were moved out to a 
> separate module (which could still be included in 
> sage-the-distribution, as at least an optional package if not a 
> standard package)? 
>
> My reasoning here is not so much that it isn't useful (which I think 
> it clearly is), but rather that it's a pretty general tool that 
> deserves to live outside Sage.  And it's also in need of maintenance, 
> which eventually will make it a blocker for Sage, which is not so good 
> given that it can clearly exist outside of Sage itself. 
>

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Piecewise affine functions

[Matthias Koeppe]

Xavier,

For code for piecewise linear functions of several variables, see 
here: 
https://github.com/mkoeppe/cutgeneratingfunctionology/blob/master/piecewise_functions.sage
I'd be quite interested in getting something like this into sage. There's 
no ticket for this yet.

Also, you might be interested in https://trac.sagemath.org/ticket/20877

Best,
Matthias

On Thursday, October 18, 2018 at 4:37:17 PM UTC-5, Xavier Caruso wrote:
>
> Hello, 
>
> For some application I have in mind (related to ticket #26471 for 
> those who are interested), I need to have support for piecewise 
> affine functions in Sage. More precisely, what I mostly need is: 
>  . to add, compose, take the sup/inf of these functions 
>  . to check continuity, convexity, bijectivity 
>  . to compute the inverse (for composition) when appropriate 
>
> I'd be happy to implement this but I'm unsure how it should fit 
> in the current framework. Notably, I noticed that there already 
> exists support for piecewise defined functions: 
>   
> http://doc.sagemath.org/html/en/reference/functions/sage/functions/piecewise.html
>  
> So I guess that I should derive from this class. 
> But I'm unsure because I realized that the behavior of piecewise 
> defined functions is sometimes a bit different for what I'd like 
> to have. For instance, if f and g are PiecewiseAffineFunction, I 
> would expect f + g to be a PiecewiseAffineFunction as well. And 
> f.derivative() as well, etc. 
> It's not exactly the case for piecewise defined function: 
>
> sage: f = piecewise([((0,1), 2*x), ([-1,0], 3*x)]) 
> sage: type(f) == type(f + f) 
> False 
> sage: type(f) == type(f.derivative()) 
> False 
>
> (I saw that there is a method piecewise_add() but I would expect 
> it to be the default __add__; why isn't it the case?) 
>
> Moreover it seems that composition of piecewise defined functions 
> is presumably broken[#] (or not implemented): 
>
> sage: f(f) 
> Traceback (most recent call last): 
> ... 
> TypeError: __call__() takes exactly 2 arguments (3 given) 
>
> sage: f(f(x)) 
> Traceback (most recent call last): 
> ... 
> TypeError: __call__() takes exactly 2 arguments (3 given) 
>
> So my question is: what should I do in order to implement piecewise 
> affine functions and the features I would like to have? Do you have 
> any good advise? 
>
> Best, 
> --Xavier 
>
> [#] By the way, I noticed: 
> sage: f(x) = 2*x + 3 
> sage: f(f) 
> 4*x + 9 
>   Shouldn't it x |--> 4*x + 9 instead? 
>

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Piecewise affine functions

[Matthias Koeppe]

Ticket (for piecewise linear functions, polyhedral domains) 
at https://trac.sagemath.org/ticket/26512


On Friday, October 19, 2018 at 4:00:53 AM UTC-5, Dima Pasechnik wrote:
>
> On Fri, Oct 19, 2018 at 4:08 AM Matthias Koeppe 
> > wrote: 
> > 
> > Xavier, 
> > 
> > For code for piecewise linear functions of several variables, see here: 
> https://github.com/mkoeppe/cutgeneratingfunctionology/blob/master/piecewise_functions.sage
>  
> > I'd be quite interested in getting something like this into sage. 
> There's no ticket for this yet. 
> > 
> assuming the interface is reasonable, the 1st task would be to convert 
> this into python (essentially, adding imports and replacing 
> Sage-specific syntax with Python 
> (e.g. ^ -> **)). 
> And then add it somewhere to sage/geometry/ 
>
> Dima 
>
>
> > Also, you might be interested in https://trac.sagemath.org/ticket/20877 
> > 
> > Best, 
> > Matthias 
> > 
> > On Thursday, October 18, 2018 at 4:37:17 PM UTC-5, Xavier Caruso wrote: 
> >> 
> >> Hello, 
> >> 
> >> For some application I have in mind (related to ticket #26471 for 
> >> those who are interested), I need to have support for piecewise 
> >> affine functions in Sage. More precisely, what I mostly need is: 
> >>  . to add, compose, take the sup/inf of these functions 
> >>  . to check continuity, convexity, bijectivity 
> >>  . to compute the inverse (for composition) when appropriate 
> >> 
> >> I'd be happy to implement this but I'm unsure how it should fit 
> >> in the current framework. Notably, I noticed that there already 
> >> exists support for piecewise defined functions: 
> >>   
> http://doc.sagemath.org/html/en/reference/functions/sage/functions/piecewise.html
>  
> >> So I guess that I should derive from this class. 
> >> But I'm unsure because I realized that the behavior of piecewise 
> >> defined functions is sometimes a bit different for what I'd like 
> >> to have. For instance, if f and g are PiecewiseAffineFunction, I 
> >> would expect f + g to be a PiecewiseAffineFunction as well. And 
> >> f.derivative() as well, etc. 
> >> It's not exactly the case for piecewise defined function: 
> >> 
> >> sage: f = piecewise([((0,1), 2*x), ([-1,0], 3*x)]) 
> >> sage: type(f) == type(f + f) 
> >> False 
> >> sage: type(f) == type(f.derivative()) 
> >> False 
> >> 
> >> (I saw that there is a method piecewise_add() but I would expect 
> >> it to be the default __add__; why isn't it the case?) 
> >> 
> >> Moreover it seems that composition of piecewise defined functions 
> >> is presumably broken[#] (or not implemented): 
> >> 
> >> sage: f(f) 
> >> Traceback (most recent call last): 
> >> ... 
> >> TypeError: __call__() takes exactly 2 arguments (3 given) 
> >> 
> >> sage: f(f(x)) 
> >> Traceback (most recent call last): 
> >> ... 
> >> TypeError: __call__() takes exactly 2 arguments (3 given) 
> >> 
> >> So my question is: what should I do in order to implement piecewise 
> >> affine functions and the features I would like to have? Do you have 
> >> any good advise? 
> >> 
> >> Best, 
> >> --Xavier 
> >> 
> >> [#] By the way, I noticed: 
> >> sage: f(x) = 2*x + 3 
> >> sage: f(f) 
> >> 4*x + 9 
> >>   Shouldn't it x |--> 4*x + 9 instead? 
> > 
> > -- 
> > 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+...@googlegroups.com . 
> > To post to this group, send email to sage-...@googlegroups.com 
> . 
> > Visit this group at https://groups.google.com/group/sage-devel. 
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Piecewise affine functions

[Matthias Koeppe]

Though it sounds like you only need piecewise functions of a single real 
variable, I would suggest to make the ticket for piecewise linear (or 
polynomial) functions of several variables.
The current implementation of piecewise in Sage is tied to the general 
symbolics in the symbolic ring. Instead, the new class would make piecewise 
functions elements of a separate parent. In my applications, I would need 
the parents to be in different categories. In the first application, it 
would be either in the category of vector spaces. In the second 
application, I would like to give this parent the category of an inverse 
semigroup: multiplication would be composition and inverse would be the 
functional inverse.

On Thursday, October 25, 2018 at 3:05:31 PM UTC-7, Xavier Caruso wrote:
>
> Le vendredi 19 octobre 2018, Matthias Koeppe a écrit : 
> > Ticket (for piecewise linear functions, polyhedral domains) at  
> > https://trac.sagemath.org/ticket/26512 
>
> Thanks for opening this ticket. 
>
> I went through your code. 
> I guess that what I need is essentialy the classes "FastLinearFunction" 
> and "FastPiecewise" (except that the latter doesn't implement composition 
> and inverse but I can probably do it by myself, at least for piecewise 
> linear functions). 
>
> However, it's still not clear to me how we should integrate this in the 
> current distribution of Sage. Your class "FastPiecewise" inherits from 
> sage.functions.piecewise_old.PiecewisePolynomial which is deprecated now. 
> Moreover, we cannot just use sage.functions.piecewise.Piecewise instead 
> since its design is different from yours (e.g. your __add__ corresponds 
> to piecewise_add, etc.) 
>
> --Xavier 
>

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Piecewise affine functions

[Matthias Koeppe]

Not sure if there should be a  class Function from which you inherit. I 
would think  PiecewiseFunctions should tie in with Sage's category 
framework. There's 
http://doc.sagemath.org/html/en/reference/categories/sage/categories/map.html#sage.categories.map.Map

On Thursday, November 8, 2018 at 2:36:40 AM UTC-8, Xavier Caruso wrote:
>
> Le lundi  5 novembre 2018, Vincent Delecroix a écrit : 
> > If you want to support composition of functions then you want to be 
> > able to take images of "nice sets" by "nice maps". In other words, 
> > you need a theory that supports quantifier elimination (see e.g. [1]). 
> > In the situation discussed by Matthias and Xavier, it is called 
> > Fourier-Motzkin elimination. 
>
> I think that taking *inverse* images are enough (which is presumably 
> a little bit simpler and does not require quantifier elimination). 
> Indeed, if f and g are piecewise functions defined respectively by: 
>   f(x) = f_i(x)  if x in I_i (for i in some set) 
>   g(x) = g_j(x)  if x in J_j (for j in some other set) 
> we have: 
>   f(g(x)) = f_i(g_j(x)) 
> when x is in the intersection of J_j and g_j^(-1)(I_i). 
>
> By the way, I noticed that there is no particular support for real 
> valued functions in Sage (except if I missed something). At least 
> End(RR) returns the "Set of *Homomorphisms* from Real Field ... to 
> Real Field ...". Shouldn't we implement this? 
> More generally, shouldn't we implement a parent for the set of all 
> set-theoretical functions from A to B (where A and B are two given 
> parents)? 
>
> So my concrete proposal would be to create a new class (say Function) 
> offering the methods inverse_image and composite (which could be not 
> implemented in all cases of course). 
> Then, we can build on this to implement PiecewiseFunctions. 
>
> Any comments? 
>
> --Xavier 
>
> PS: Should we continue to discuss this on sage-devel or it is better 
> to move to trac (which ticket)? 
>

-- 
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.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: pip-21.1.2 compile fails on MacOS

[Matthias Koeppe]

I have added this as a task to https://trac.sagemath.org/ticket/30453

On Friday, November 12, 2021 at 2:17:05 PM UTC-8 Matthias Koeppe wrote:

> No, we should revise the documentation so that it does not advertise "make 
> test" any more.
>
> On Friday, November 12, 2021 at 2:09:12 PM UTC-8 Dima Pasechnik wrote:
>
>> On Friday, November 12, 2021 at 8:20:24 PM UTC Matthias Koeppe wrote:
>>
>>> Yes, if one is not using the Sage distribution for build, one should 
>>> also not use it for testing.
>>> Use "sage -t".
>>>
>>
>> that's not nice. Should we have a ./configure option that just blesses 
>> all deps as "coming from the system"?
>>
>>
>>
>>>
>>> On Friday, November 12, 2021 at 10:39:47 AM UTC-8 Dima Pasechnik wrote:
>>>
>>>> On Fri, Nov 12, 2021 at 5:01 PM Matthias Koeppe 
>>>>  wrote: 
>>>> > 
>>>> > On Friday, November 12, 2021 at 2:42:09 AM UTC-8 Dima Pasechnik 
>>>> wrote: 
>>>> >> 
>>>> >> On Friday, November 12, 2021 at 6:36:00 AM UTC Matthias Koeppe 
>>>> wrote: 
>>>> >>> 
>>>> >>> I have updated the instructions. 
>>>> >> 
>>>> >> 
>>>> >> Thanks - are these tested? 
>>>> > 
>>>> > 
>>>> > Yes, I tested them on macOS Big Sur. 
>>>>
>>>> hmm, by design, or in error, "make ptest" starts building all the 
>>>> dependencies, e.g. maxima. 
>>>> So that's not a usual environment - perhaps it should be mentioned. 
>>>>
>>>>
>>>> > 
>>>> > 
>>>> > 
>>>> > -- 
>>>> > 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+...@googlegroups.com. 
>>>> > To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/sage-devel/7cffbfcd-ef4c-48a4-a2ae-126677315662n%40googlegroups.com.
>>>>  
>>>>
>>>>
>>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e5edb1b7-3459-438e-b679-1a284d338950n%40googlegroups.com.

[sage-devel] Re: Master plan of sage modularization

[Matthias Koeppe]

That would be https://trac.sagemath.org/ticket/29705

Help with documenting the principles and goals of modularization in the 
developer's guide is definitely very welcome!

On Wednesday, November 17, 2021 at 6:27:56 PM UTC-8 Kwankyu Lee wrote:

> Hi,
>
> Sage modularization is going on, and I see in trac many tickets toward the 
> goal. But I wonder what is the master plan. I mean the plan how sage 
> library  would be split. Here and there I read that some packages in the 
> sage library will be namespace packages, and others won't be. It would be 
> nice to have the master plan at one place. Perhaps this information needs 
> to be included in the developer manual.  If there is a plan laid out, where 
> is it?
>
> Thanks for attention.
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0c8d550f-bb5a-4ae5-aa24-37944548738an%40googlegroups.com.

[sage-devel] Re: Master plan of sage modularization

[Matthias Koeppe]

On Wednesday, November 17, 2021 at 10:01:47 PM UTC-8 Kwankyu Lee wrote:

> On Thursday, November 18, 2021 at 11:47:37 AM UTC+9 Matthias Koeppe wrote:
>
>> That would be https://trac.sagemath.org/ticket/29705
>
>
> Yes, all the information could be found in the ticket description and the 
> descriptions of the subtickets. But the master plan is buried in the 
> details. I want to see how the whole sage library would be split into what 
> distributions at the end of the modularization effort, and how the 
> distributions depend on another if any.   
>

The design of the distributions is not completely settled. I am hoping that 
Interested developers will join the effort in completing the design.

Hard constraints on the distributions come from compile-time dependencies 
of Cython modules on C/C++ libraries. 
We can define some meaningful small distributions that just consist of a 
single or a few Cython modules. For example, *sagemath-tdlib* 
(https://trac.sagemath.org/ticket/29864) would just package the single 
Cython module that must be linked with tdlib, 
sage.graphs.graph_decompositions.tdlib. In the Sage 9.6 cycle, as soon as 
namespace packages are activated (by dropping __init__.py files), we can 
start to create these distributions. This is quite a mechanical task -- for 
each distribution it's just a new directory in pkgs/ with some metadata 
files.

Let me sketch my strategy to get closer to the design of other 
distributions. https://trac.sagemath.org/ticket/29865 (waiting for review) 
introduces the two lowest levels - *sagemath-objects*, 
*sagemath-categories.* As soon as we have namespace packages working, the 
latter will depend on the former. The current issue with both of these 
distributions is that they are not really separately testable because the 
doctests for these modules depend on a lot of other functionality from 
higher-level parts of the library. In contrast, in 
https://trac.sagemath.org/ticket/32432, we are working on a medium-sized 
distribution *sagemath-polyhedra*, which be the first modularized 
distribution that is useful for end users. It will also be sufficiently 
self-contained for running most doctests (but some doctests that depend on 
other parts of the library are marked # optional). Between *sagemath-categories 
*and *sagemath-polyhedra *(which depends on *sagemath-categories*) there is 
room for designing intermediate distributions. For example, there could be 
a distribution that contains the linear algebra needed by 
*sagemath-polyhedra* (i.e., parts of the sage.modules and sage.matrix).

At the coarsest level, *sagemath-symbolics 
(*https://trac.sagemath.org/ticket/31695) 
and *sagemath-standard-no-symbolics *(https://trac.sagemath.org/ticket/32601) 
are intended to form a partition of all Sage standard library modules that 
are not already in *sagemath-categories *(or its dependencies). Below these 
two distributions, again there is room for designing various intermediate 
distributions. The design will be best if done by (or in ollaboration with) 
developers who are knowledgable about specific parts of the Sage library 
corresponding to the various areas of mathematics.


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/99a02ddf-5f6a-4973-a15d-7ca927bfd12en%40googlegroups.com.

[sage-devel] Re: Master plan of sage modularization

[Matthias Koeppe]

On Wednesday, November 17, 2021 at 11:48:04 PM UTC-8 Kwankyu Lee wrote:

> For example, if there would be a distribution sagemath-coding that 
>> contains sage/coding, then would we have this hierarchy 
>>
>
> sagemath-objects < sagemath-categories < sagemath-standard-no-symbolics < 
> ... < sagemath-coding
>  
> where ... might be filled with other intermediate distributions like, I 
> imagine, sagemath-rings, sagemath-schemes?
>

OK, let's take a look at sage.coding. 

First, let's see if it uses symbolics. 

(9.5.beta6) $ git grep -E 'sage[.](symbolic|functions|calculus)' 
src/sage/coding
src/sage/coding/code_bounds.py:from sage.functions.other import ceil
src/sage/coding/code_bounds.py:sage: 
codes.bounds.entropy(1/5,4).factor()# optional - sage.symbolic
src/sage/coding/code_bounds.py:sage: codes.bounds.entropy(1, 3)
  # optional - sage.symbolic
src/sage/coding/grs_code.py:from sage.functions.other import binomial
src/sage/coding/grs_code.py:from sage.symbolic.ring import SR
src/sage/coding/guruswami_sudan/gs_decoder.py:from sage.functions.other 
import floor
src/sage/coding/guruswami_sudan/utils.py:from sage.functions.other import 
floor

Apparently it does not in a very substantial way 
- The imports of ceil and floor can likely be replaced by integer_floor, 
integer_ceil from sage.arith.misc.
- Looking at the import of SR by src/sage/coding/grs_code.py, it seems that 
SR is used for running some symbolic sum, but the doctests do not show 
symbolic results, so it is likely that this can be replaced. 
- Note though that the above textual search for the module names is merely 
a heuristic. Looking at the source of "entropy", through "log" from 
sage.misc.functional, a runtime dependency on symbolics comes in. (I have 
already marked 2 doctests there as # optional - sage.symbolic.)

So if packaged as *sagemath-coding, *now a domain expert would have to 
decide whether these dependencies on symbolics are strong enough to declare 
a runtime dependency ("install_requires") on *sagemath-symbolics. *This 
declaration would mean that anyone who installs *sagemath-coding* ("pip 
install sagemath-coding") would pull in *sagemath-symbolics* ... which, at 
least currently, has heavy compile-time dependencies 
(ECL/Maxima/FLINT/Singular...).
The alternative is to consider the use of symbolics by *sagemath-coding* 
merely as something that provides some extra features ... which will only 
be working if the user also has installed *sagemath-symbolics. (*It is 
possible to declare this as an "extras_require" so that users could go "pip 
install sagemath-coding[symbolics]".) 

Let's say that we go with the second alternative. Then *sagemath-coding* would 
be a dependency of *sagemath-standard-no-symbolics*.
So it would look like this:

*sagemath-objects* < *sagemath-categories* < *sagemath-coding* < 
*sagemath-standard-no-symbolics* < *sagemath-standard*

In general, would this hierarchy have a tree structure?
>

No, only directed acyclic. For example, another chain is

*sagemath-objects* < *sagemath-categories* < *sagemath-symbolics* < 
*sagemath-standard*


As to other distributions that you asked about, yes, *sagemath-schemes* 
could be a good distribution, but I am not sure where it would go in this 
picture because sage.schemes is not homogeneous in terms of its 
dependencies. For example, sage.schemes.[hyper]elliptic_curves seems to 
make heavy use of symbolics, whereas sage.schemes.toric is closely 
connected to sage.geometry. So smaller distributions along the lines of 
dependencies could make sense as well.

We will most likely not have a distribution *sagemath-rings. *The reason is 
that the various ring element implementations pull in a wide spectrum of 
compiled libraries, so *sagemath-rings *would be nearly as monolithic as 
all of Sage. More useful could be smaller distributions, again informed by 
dependencies, such as *sagemath-padics*, for example: Most current uses of 
the NTL library in Sage seem to be for sage.rings.padics. 


 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/def60633-ed17-4426-9492-b9638c0c0048n%40googlegroups.com.

[sage-devel] Re: Master plan of sage modularization

[Matthias Koeppe]

On Thursday, November 18, 2021 at 5:37:13 PM UTC-8 Kwankyu Lee wrote:

> On Friday, November 19, 2021 at 2:59:55 AM UTC+9 Matthias Koeppe wrote:
>
>> ... So it would look like this:
>>
>
>> *sagemath-objects* < *sagemath-categories* < *sagemath-coding* < 
>> *sagemath-standard-no-symbolics* < *sagemath-standard*
>>
>>
> package sage.coding needs linear algebra, all kinds of fields, and 
> algebraic curves, etc.
>

Yes, these would have to be provided by dependencies of *sagemath-coding*, 
i.e., something between *sagemath-categories* and *sagemath-coding*. The 
names and design of these distributions are not settled yet. For example, 
below *sagemath-coding* and *sagemath-polyhedra* (but above 
*sagemath-categories*) there should be a distribution that provides linear 
algebra over basic rings and fields. This could be a subset of what (at the 
moment) goes into *sagemath-polyhedra* as developed in 
https://trac.sagemath.org/ticket/32432
 

>   Hence I thought sagemath-standard-no-symbolics (or whatever that 
> includes all packages that sage.coding depends on) should precede 
> sagemath-coding in the diagram. 
>

Installing *sagemath-standard-no-symbolics* is intended to provide 
"everything that is right now in the Sage library without depending on 
optional packages, but without sage.symbolic etc." This would include (as a 
dependency) *sagemath-coding.*


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/6a10f79d-467b-4d05-a15e-01b728edfda6n%40googlegroups.com.

[sage-devel] Re: Master plan of sage modularization

[Matthias Koeppe]

On Thursday, November 18, 2021 at 8:05:26 PM UTC-8 Kwankyu Lee wrote:

> Questions on "Features":
>
> We are introducing Features for packages in the sage library, like 
> sage__combinat, sage__graphs, sage__plot, etc. How is this related with 
> distributions? If a package is included in a distribution (other than 
> sagemath-standard), a Feature for the package is introduced?
>
> Can(Do) we use doctest tags for optional packages like, for example, # 
> optional - sage.plot only when a Feature for the package (sage.plot) exists?
>

Yes, that's the mechanism. A feature's name is used as the doctest tag. 

These features are explicitly declared in a single file, 
src/sage/features/sagemath.py, and we would add the mapping from features 
to the distributions providing them (actually, to SPKG names) there as 
well. Using this mapping, we can then start to give installation hints to 
the user.

Thus whether we use such tags for certain doctests ultimately depend on how 
> we organize the distributions? 
>

Yes, but hopefully it will be relatively stable because of the decision to 
key the doctest tags to package names rather than distribution names.
 

> Perhaps the organization of these distributions would constantly evolve.  
> And hence we would add such tags more and more? 
>

Yes, this will likely take a while to stabilize. 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/2f86f87f-a2f7-444f-aa51-029ede6ae62fn%40googlegroups.com.

[sage-devel] Re: How to modularize for fun and profit, II: MONOREPO vs. MULTIREPO

[Matthias Koeppe]

On Sunday, October 10, 2021 at 5:17:33 PM UTC-7 Matthias Koeppe wrote:

> - Even for separate git repositories hosted in the SageMath GitHub 
> organization (https://github.com/sagemath/), code ownership and review 
> workflow are unclear.
>   - For example, https://github.com/sagemath/sage-numerical-backends-coin 
> provides no information on how to contribute (commonly expected in a file 
> CONTRIBUTING.md)
>   - Neither does https://github.com/sagemath/cysignals, which moreover 
> looks abandoned: Issues and PRs are not tended to. Is it subject to peer 
> review like other parts of Sage? Who is in charge of merging PRs?
>   - Similar issues with https://github.com/sagemath/cypari2
>

These issues are still unresolved.
In the meantime I have added @kliem to the list of cysignals and cypari2 
admins so that we can make progress on the pressing portability issues.



 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/3bfbc842-74ab-4093-bef2-55f9e2c0fdffn%40googlegroups.com.

[sage-devel] Re: Demote SageTeX to an optional package?

[Matthias Koeppe]

-1 on demoting it from standard. It's tiny, and installing it as part of 
the distribution is unproblematic. 

-1 on adding a Sage-specific installation procedure for TeX. Actually, we 
already have one but there is no good reason to use it other than possibly 
as part of the binary distribution; https://trac.sagemath.org/ticket/31529 
proposes to remove it.

+1 on exploring and documenting alternatives that are not tied to Sage.


On Monday, December 6, 2021 at 1:55:38 AM UTC-8 emanuel.c...@gmail.com 
wrote:

> Having a *standard* way to integrate Sage’s results in a document is 
> **crucial*.
>
> So -1.
>
> Counter-proposal : add a pseudo-package à la tinytex 
>  (which tests 
> for a local TeX installation, and install a minimal TeX if necessary).
>
> Other possible alternatives : PythonTeX 
>  (slightly more general, accepts 
> more languages), codebraid  (a 
> budding equivalent to PythonTeX using Markdown as a markup language). The 
> latter may become important, Markdown turning out to be much more popular 
> than LaTeX nowadays (notwithstanding its severe limitations).
>
> Possible addition : professionals mathematicians do not need a LaTeX 
> introduction, but students and “engineering type” users might benefit from 
> a “Presenting Sage work” section in our tutorials.
> ​
> Le lundi 6 décembre 2021 à 01:02:12 UTC+1, Michael Orlitzky a écrit :
>
>> SageTeX was added to sage as a standard package in 
>>
>> https://trac.sagemath.org/ticket/7617 
>>
>> It's closely tied to sage (can't be used on its own), but is also not 
>> used by any other part of sage. 
>>
>> Can we demote it to an optional package? Realistically this amounts to 
>> adding "first, run `make sagetex`" at the top of the docs that talk 
>> about it (warning: requires translators). 
>>
>> The benefits are the usual ones: faster installation, less disk usage, 
>> easier for distros to package a standard "sage". And the downside of 
>> course is that anyone regularly using sagetex will have to either 
>> ./configure --enable-sagetex, or run "make sagetex" at some point. 
>>
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/2ca7be82-9173-4db5-86bc-4ceb9854d6f5n%40googlegroups.com.

[sage-devel] ask.sagemath.org issues - do we need it?

[Matthias Koeppe]

I have received a report that ask.sagemath.org account management is broken:
> das "recover account" jedoch funktioniert jedoch nicht.
> wenn man auf den button klickt passiert lange nichts, und irgendwann "504 
Gateway Time-out".

I don't normally use ask.sagemath.org myself, but to reproduce the reported 
error, I've tried logging in using Google and also eventually got a 504.
https://ask.sagemath.org/account/signin/complete-oauth2/?state=&scope=email+profile+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.profile+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email+openid&authuser=0&prompt=consent#

Overall, I am not sure why the project is running this server. I think we 
are spreading ourselves pretty thin here. There is also:
- https://groups.google.com/g/sage-support
- https://stackoverflow.com/questions/tagged/sage
- https://stackexchange.com/search?q=sage
- https://mathoverflow.net/search?q=sage

Is any of the information at 
https://wiki.sagemath.org/Infrastructure#ask.sagemath.org still current?






-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/da62341d-d157-405c-9ea1-ea5f316d54c7n%40googlegroups.com.

[sage-devel] Re: ask.sagemath.org issues - do we need it?

[Matthias Koeppe]

On Saturday, December 11, 2021 at 7:00:54 AM UTC-8 kcrisman wrote:

>  As for sage-support, it's always surprising to me how many "customers" 
> simply disappear as soon as you mention asking a question there - somehow 
> they either want a Q&A site, or to ask on Facebook, or whatever.  I don't 
> really know why this happens, but clearly the Q&A sites (in toto) are 
> necessary.
>
>
Another option may be to move to Discourse. Many projects use it, 
including https://discuss.python.org/ and https://discourse.julialang.org/

https://meta.discourse.org/t/easy-way-to-migrate-askbot-to-discourse/148677

 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/2edca99e-0c87-4eb8-8faf-d401de116f9an%40googlegroups.com.

[sage-devel] trac.sagemath.org down

[Matthias Koeppe]

git and trac appear to be down

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e2491638-9f36-4144-a9b2-45326a973fb2n%40googlegroups.com.

Re: [sage-devel] trac.sagemath.org down

[Matthias Koeppe]

Many thanks to all who are keeping our project infrastructure going!

On Saturday, December 11, 2021 at 3:40:25 PM UTC-8 wst...@gmail.com wrote:

> It should now be fixed. There was a mysterious issue with the Google Cloud 
> Billing account getting unset, so I fixed that.
>
> William
>
> On Sat, Dec 11, 2021 at 2:39 PM Dima Pasechnik  wrote:
>
>> On Sat, Dec 11, 2021 at 10:11 PM Matthias Koeppe
>>  wrote:
>> >
>> > git and trac appear to be down
>>
>> There is a biling screw-up going on with it.
>>
>> Dima
>> >
>> > --
>> > 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+...@googlegroups.com.
>> > To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/e2491638-9f36-4144-a9b2-45326a973fb2n%40googlegroups.com
>> .
>>
>> -- 
>> 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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/CAAWYfq1_LGTG9LO%2BvD6uzX2ni2SOKxUbqbBy2693TC1C9Tr1KQ%40mail.gmail.com
>> .
>>
>
>
> -- 
> William (http://wstein.org)
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/c130a700-90f9-40eb-afcf-718213c31a48n%40googlegroups.com.

[sage-devel] Re: https://wiki.sagemath.org/ReleaseTours/sage-9.5

[Matthias Koeppe]

On Tuesday, November 2, 2021 at 12:37:01 PM UTC-7 Matthias Koeppe wrote:

> It's time to work on the release tour for Sage 9.5:
> https://wiki.sagemath.org/ReleaseTours/sage-9.5
> If you don't have an account that allows you to edit the wiki, please feel 
> free to just post additions as a reply here; I can add them to the page.
>

So far we have:

Contents

   1. Sage 9.5 Release Tour 
   <https://wiki.sagemath.org/ReleaseTours/sage-9.5#Sage_9.5_Release_Tour>
  1. Symbolics 
  <https://wiki.sagemath.org/ReleaseTours/sage-9.5#Symbolics>
 1. Changes to symbolic expressions 
 
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Changes_to_symbolic_expressions>
 2. Interface to Mathics, a free implementation of the Wolfram 
 language 
 
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Interface_to_Mathics.2C_a_free_implementation_of_the_Wolfram_language>
  2. Linear Algebra 
  <https://wiki.sagemath.org/ReleaseTours/sage-9.5#Linear_Algebra>
  3. Manifolds 
  <https://wiki.sagemath.org/ReleaseTours/sage-9.5#Manifolds>
  4. Number theory 
  <https://wiki.sagemath.org/ReleaseTours/sage-9.5#Number_theory>
 1. Elliptic curves and isogenies 
 
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Elliptic_curves_and_isogenies>
 2. Modular and quasimodular forms 
 
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Modular_and_quasimodular_forms>
  5. Algebra <https://wiki.sagemath.org/ReleaseTours/sage-9.5#Algebra>
 1. New lazy Laurent series backend 
 
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#New_lazy_Laurent_series_backend>
 2. Lazy Dirichlet series 
 <https://wiki.sagemath.org/ReleaseTours/sage-9.5#Lazy_Dirichlet_series>
  6. Deprecated and removed functionality 
  
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Deprecated_and_removed_functionality>
  7. Package upgrades 
  <https://wiki.sagemath.org/ReleaseTours/sage-9.5#Package_upgrades>
  8. Configuration changes 
  <https://wiki.sagemath.org/ReleaseTours/sage-9.5#Configuration_changes>
 1. Separate virtual environment for Python packages 
 
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Separate_virtual_environment_for_Python_packages>
 2. New default: configure --with-system-gcc=force 
 
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#New_default:_configure_--with-system-gcc.3Dforce>
 3. Packages atlas and mpir removed 
 
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Packages_atlas_and_mpir_removed>
  9. Modularization and packaging changes 
  
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Modularization_and_packaging_changes>
 1. New distribution package: sage-setup 
 
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#New_distribution_package:_sage-setup>
 2. Pynac merged into the Sage library 
 
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Pynac_merged_into_the_Sage_library>
 3. Doctest annotation "# optional - FEATURE" for portions of the 
 Sage library 
 
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Doctest_annotation_.22.23_optional_-_FEATURE.22_for_portions_of_the_Sage_library>
 4. Module-level annotation "# sage.doctest: optional - FEATURE" 
 
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Module-level_annotation_.22.23_sage.doctest:_optional_-_FEATURE.22>
 5. Abstract base classes for "isinstance" testing 
 
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Abstract_base_classes_for_.22isinstance.22_testing>
  10. Availability of Sage 9.5 and installation help 
  
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Availability_of_Sage_9.5_and_installation_help>
  11. More details 
  <https://wiki.sagemath.org/ReleaseTours/sage-9.5#More_details>
   

 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/28ecdcf2-696f-45ee-bffa-30476e9181e7n%40googlegroups.com.

[sage-devel] Re: First impressions on Sage 9.4 source build

[Matthias Koeppe]

On Friday, December 17, 2021 at 2:33:55 PM UTC-8 Randall wrote:

> I am building sage version 9.4 from source on my OpenSuse Linux Leap 15.2 
> OS and like the install document stated, it has taken hours (using a HP 
> Z420 workstation with 6 Xeon processors) 
>
> [...]
> 2. I noticed that sage recommended several OpenSuse system packages on the 
> zypper install line, but I did run this and believe it or not, nothing was 
> available.
>

Your distro is too old. Consider updating to Leap 15.3 or use OpenSuse 
Tumbleweed.

 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d9205800-08c1-466d-aaab-b63c797c9463n%40googlegroups.com.

[sage-devel] Re: Compilation failed due to linbox

[Matthias Koeppe]

Post config.log please

On Saturday, December 18, 2021 at 5:21:54 AM UTC-8 kilo...@gmail.com wrote:

> First, I am sorry for the duplicate with ask.sagemath.org but I feel this 
> website is better and easier to share a log (and it was indicated to post 
> here in the log !).
>
> I tried to recompile Sage on my Archlinux Virtual Machine, after a system 
> upgrade (pikaur -Syu) upgraded my Python from 3.9.8 (or 3.9.7 I do not 
> remember) to 3.10.1 .
>
> I tried many attempts, by removing the directory, recompile with a `make 
> distclean && make`, by compiling the SageMath stable version (master 
> branch) as well as the (develop branch).
>
> The last thing I tried was, as instructed on github page 
> https://github.com/sagemath/sage/ :
> git clone -c core.symlinks=true https://github.com/sagemath/sage.git
> cd sage && git checkout develop
> ./configure
> make
>
> After 1/2 hour, the compilation fails with an error related to the build 
> process of one SPKGs linbox:
> I made a pastebin of the log https://pastebin.com/gbDk2m2u, and I 
> attached the log
> I tried to install system wide linbox package with my package manager 
> (pacman).
> The pacman version is greater than the one Sagemath tries to build (1.7 
> rather than 1.6).
> The ./configure did not change the compilation (it did not detect the 
> linbox package).
>
> What can I do ? Any answer is appreciated
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/b45b8b97-6023-4a48-8533-36d55a019140n%40googlegroups.com.

[sage-devel] Re: Compilation failed due to linbox

[Matthias Koeppe]

Try if "./configure --without-system-givaro" fixes this problem for you.

This is likely the issue described in https://trac.sagemath.org/ticket/33042


On Saturday, December 18, 2021 at 5:21:54 AM UTC-8 kilo...@gmail.com wrote:

> First, I am sorry for the duplicate with ask.sagemath.org but I feel this 
> website is better and easier to share a log (and it was indicated to post 
> here in the log !).
>
> I tried to recompile Sage on my Archlinux Virtual Machine, after a system 
> upgrade (pikaur -Syu) upgraded my Python from 3.9.8 (or 3.9.7 I do not 
> remember) to 3.10.1 .
>
> I tried many attempts, by removing the directory, recompile with a `make 
> distclean && make`, by compiling the SageMath stable version (master 
> branch) as well as the (develop branch).
>
> The last thing I tried was, as instructed on github page 
> https://github.com/sagemath/sage/ :
> git clone -c core.symlinks=true https://github.com/sagemath/sage.git
> cd sage && git checkout develop
> ./configure
> make
>
> After 1/2 hour, the compilation fails with an error related to the build 
> process of one SPKGs linbox:
> I made a pastebin of the log https://pastebin.com/gbDk2m2u, and I 
> attached the log
> I tried to install system wide linbox package with my package manager 
> (pacman).
> The pacman version is greater than the one Sagemath tries to build (1.7 
> rather than 1.6).
> The ./configure did not change the compilation (it did not detect the 
> linbox package).
>
> What can I do ? Any answer is appreciated
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/b24d8ff5-0996-42c0-aa34-cb55c3eb9939n%40googlegroups.com.

[sage-devel] Re: \Bold command definition in every LaTeX output

[Matthias Koeppe]

On Tuesday, December 21, 2021 at 2:49:11 AM UTC-8 Eric Gourgoulhon wrote:

> Unless there might be a reason for it, why not replacing lines like
> return r"\Bold{Q}"
> by
> return r"\mathbf{Q}"
> in the relevant  _latex_ methods ? 
>

+1

 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f4ae357d-244c-4e53-84f1-c0cda7d8a16fn%40googlegroups.com.

[sage-devel] Re: \Bold command definition in every LaTeX output

[Matthias Koeppe]

On Tuesday, December 21, 2021 at 3:26:58 PM UTC-8 John H Palmieri wrote:

> I have no objection to this, but the purpose for using \Bold{...} was to 
> make its behavior easily customizable, since some people might want 
> \mathbf{...} and some might want \mathbb{...}. 
>

If we are keeping \Bold for this purpose, perhaps we should change 
\newcommand to \providecommand, which would fix OP's issue 
 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/b915d9df-6ee1-46d3-99b8-3a1c7f62843dn%40googlegroups.com.

[sage-devel] Re: Source Build Fails on GCC-10

[Matthias Koeppe]

Don't try to mix system packages and conda packages. 
Pick a method.
Either work with Debian packages (apt-get) and deactivate all conda. 
Or set up and activate the conda environment; and don't try to override 
compilers.
Also, do not use "./configure --prefix=$CONDA_PREFIX" -- this is not 
supported because Sage packages could overwrite conda-installed packages.

On Wednesday, December 22, 2021 at 10:40:30 AM UTC-8 jorda...@gmail.com 
wrote:

> I'm trying to build SageMath from source on Ubuntu 20.04. Below is the 
> exact process I tried to follow (taking notes to be able to pass to other 
> students with little/no linux experience--like me--so I try to explain each 
> step), but the build crashed on trying to build gcc-10 with "undefined 
> reference to ZSTD_compress" and a bunch of other ZSTD-related items. 
> Looking deeper into the config log, it turns out that the gcc's I supplied 
> don't manifest the OpenMC flags ("unknown"), causing it to assume it needs 
> to build it. But when I tested the supplied compilers on a "hello world 
> " .c file 
> using "[gcc-7 | gcc-10] hello.c -fopenmp -o hello", it compiled without 
> error, suggesting it has OpenMC available.
>
> So two questions: why doesn't the below install all needed dependencies 
> for the installer gcc-10 build, and more importantly, why can't ./configure 
> figure out that the compiler I gave it supports OpenMC? Thanks!
>
>- This method will install a new sage python environment that will 
>show up in our anaconda-navigator called sage-pyenv.
>- 
>
>Install all the prerecs. Highly recommended ones for better experience 
>are after *yasm*; optional ones to speed up build time after *tk-dev* 
>(Note: gcc, g++, and gfortran installed to /usr/bin/):
>
>sudo apt-get install bc binutils bzip2 ca-certificates cliquer cmake 
>curl ecl eclib-tools fflas-ffpack flintqs g++ gcc gfan gfortran glpk-utils 
>gmp-ecm lcalc libatomic-ops-dev libboost-dev libbraiding-dev libbrial-dev 
>libbrial-groebner-dev libbz2-dev libcdd-dev libcdd-tools libcliquer-dev 
>libcurl4-openssl-dev libec-dev libecm-dev libffi-dev libflint-arb-dev 
>libflint-dev libfreetype6-dev libgc-dev libgd-dev libgf2x-dev libgiac-dev 
>libgivaro-dev libglpk-dev libgmp-dev libgsl-dev libhomfly-dev libiml-dev 
>liblfunction-dev liblrcalc-dev liblzma-dev libm4rie-dev libmpc-dev 
>libmpfi-dev libmpfr-dev libncurses5-dev libntl-dev libopenblas-dev 
>libpari-dev libpcre3-dev libplanarity-dev libppl-dev libpython3-dev 
>libreadline-dev librw-dev libsqlite3-dev libssl-dev libsuitesparse-dev 
>libsymmetrica2-dev libz-dev libzmq3-dev libzn-poly-dev m4 make nauty 
>openssl palp pari-doc pari-elldata pari-galdata pari-galpol pari-gp2c 
>pari-seadata patch perl pkg-config planarity ppl-dev python3 python3 
>python3-distutils r-base-dev r-cran-lattice sqlite3 sympow tachyon tar tox 
>xcas xz-utils *yasm* gcc-7 g++-7 gfortran-7 dvipng ffmpeg imagemagick 
>texlive texlive-latex-recommended texlive-latex-recommended-doc 
>texlive-fonts-recommended texlive-fonts-recommended-doc texlive-xetex 
>latexmk pandoc default-jdk libavdevice-dev tk *tk-dev* coinor-cbc 
>coinor-libcbc-dev git graphviz libfile-slurp-perl libigraph-dev libisl-dev 
>libjson-perl libmongodb-perl libnauty-dev libperl-dev libsvg-perl 
>libterm-readkey-perl libterm-readline-gnu-perl libterm-readline-gnu-perl 
>libxml-libxslt-perl libxml-writer-perl libxml2-dev libxml2-dev lrslib 
>ninja-build pari-gp2c
>- 
>
>Get the source code:
>
>mkdir ~/Codes
>
>cd ~/Codes
>
>git clone -c core.symlinks=true --branch master 
>https://github.com/sagemath/sage.git
>- 
>
>Set up Python environment:
>
>cd ~/Codes/sage
>
>./bootstrap
>- After building the environment, I was told that conda went ahead and 
>   built the environment as Python 3.10, which is too new for Sage. Per 
> this 
>   post 
>   
> , 
>   3.8 and 3.9 are supported. It will build a 3.9 during build. So, tweak 
> some 
>   things to make sure we get that version.
>   - Go into ~/Codes/sage/environment-optional.yml, and 
>  - change the environment name to sage-pyenv
>  - add python=3.9 to dependencies, per this post 
>  
> 
>   
>conda env create -f environment-optional.yml
>
>conda activate sage-pyenv
>- 
>
>Build it:
>
>./bootstrap
>- Point it to system 
>   
> 
>  
>   gcc-7 and fortran-7 for compilation, since it seems to fail when trying 
> to 
>   b

[sage-devel] Re: Source Build Fails on GCC-10

[Matthias Koeppe]

On Thursday, December 23, 2021 at 8:51:37 AM UTC-8 jorda...@gmail.com wrote:

> Is Conda installing executable / binaries of packages in its environments, 
> not just python packages? 
>

Yes.
 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/78a51d7d-2175-4bae-b875-0b4f9176a4e2n%40googlegroups.com.

Re: [sage-devel] Re: Outdated instructions in "git the hard way"

[Matthias Koeppe]

I have made some of the suggested changes 
in https://trac.sagemath.org/ticket/29784, needs review.

On Monday, September 13, 2021 at 8:58:34 AM UTC-7 Matthias Koeppe wrote:

> OK who's going to push the first commit to the ticket 
> https://trac.sagemath.org/ticket/29784 ?
>
> On Monday, September 13, 2021 at 6:35:40 AM UTC-7 Thierry 
> (sage-googlesucks@xxx) wrote:
>
>> Hi,
>>
>> On Mon, Sep 13, 2021 at 02:05:36PM +0100, Dima Pasechnik wrote:
>> > On Fri, 10 Sep 2021, 19:39 Simon King,  wrote:
>> > 
>> > > Hi Dima,
>> > >
>> > > On 2021-09-09, Dima Pasechnik  wrote:
>> > > > I think that 'git trac' is mainly used by the release manager - I
>> > > > won't recommend it to newcomers.
>> > >
>> > > No, I'm not a release manager, but I find it very practical to be able
>> > > to do "git trac pull 12345" instead of doing a series of commands that
>> > > I simply don't manage to memorise.
>> > >
>> > 
>> > assuming that "trac" points to our Git server (as it normally done) 
>> this is
>> > just
>> > 
>> > git pull trac 
>>
>>
>> This is not "just": your suggestion hides the fact that you have to
>> copy/paste the name of the ticket branch from a webbrowser, which is
>> boring and takes time.
>>
>> The point of the "git trac" command is to link git branches with trac
>> tickets, so that you do not have to do it by hand.
>>
>> Ciao,
>> Thierry
>>
>>
>>
>>
>> > 
>> > > Best regards,
>> > > Simon
>> > >
>> > > --
>> > > 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+...@googlegroups.com.
>> > > To view this discussion on the web visit
>> > > 
>> https://groups.google.com/d/msgid/sage-devel/shg8p9%2445p%241%40ciao.gmane.io
>> > > .
>> > >
>> > 
>> > -- 
>> > 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+...@googlegroups.com.
>> > To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/CAAWYfq3%3Dk9aMWaXPv%2BpGrXtq0rv3VWFESKa5YswnhVvK_3gL2g%40mail.gmail.com
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/ca775a9d-aa39-4a33-9d56-b069221fbb3dn%40googlegroups.com.

Re: [sage-devel] sagemath 9.5beta9 fails to compile on opensuse tumbleweed

[Matthias Koeppe]

These flags likely come in through the sysconfig of the system python. 
Check "python3 -m sysconfig | grep CFLAGS"

On Monday, December 27, 2021 at 5:01:38 AM UTC-8 Dima Pasechnik wrote:

> Your compiler settings are stricter that usual.
>
> Try
>
> CXXFLAGS="$CXXFLAGS -Wno-error=return-type" CFLAGS=$CFLAGS
> -Wno-error=return-type" make build
>
> On Mon, Dec 27, 2021 at 12:41 PM 'Florian Hanisch' via sage-devel
>  wrote:
> >
> > > probably the error is in building sagelib.
> > > Look in logs/pkgs/sagelib-9.5.beta9.log
> >
> > Thanks a lot, this log file indeed ends on an error message (still have 
> to figure out what exactly went wrong here):
> >
> > error: Command "gcc -Wno-unused-result -Wsign-compare -DNDEBUG -O2 -Wall 
> -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables 
> -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type 
> -g -DOPENSSL_LOAD_CONF -fwrapv -fno-semantic-interposition -O2 -Wall 
> -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables 
> -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type 
> -g -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables 
> -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type 
> -g -g -O2 -fPIC -I./sage/ext -I./sage/cpython -I./sage/rings/finite_rings 
> -I/home/fhanisch/programs/sage/sage-9.5.beta9/local/var/lib/sage/venv-python3.8/lib64/python3.8/site-packages/cysignals
>  
> -I./sage/libs/flint -Isage/cpython 
> -I/home/fhanisch/programs/sage/sage-9.5.beta9/pkgs/sagemath-standard 
> -I/usr/include/python3.8 
> -I/home/fhanisch/programs/sage/sage-9.5.beta9/local/var/lib/sage/venv-python3.8/lib64/python3.8/site-packages/numpy/core/include
>  
> -Ibuild/cythonized 
> -I/home/fhanisch/programs/sage/sage-9.5.beta9/local/var/lib/sage/venv-python3.8/include
>  
> -I/usr/include/python3.8 -c 
> build/cythonized/sage/matrix/matrix_modn_dense_float.cpp -o 
> build/temp.linux-x86_64-3.8/build/cythonized/sage/matrix/matrix_modn_dense_float.o
>  
> -fno-strict-aliasing -DCYTHON_CLINE_IN_TRACEBACK=1 -O2 -Wall -g -DNDEBUG 
> -U_LB_DEBUG -DDISABLE_COMMENTATOR -fopenmp -DFFLAS_COMPILED 
> -DFFPACK_COMPILED -fabi-version=6 -std=gnu++11" failed with exit status 1
> >
> > The log file moreover contains the following (not critical ?) error 
> message at several places:
> >
> > 
> /home/fhanisch/programs/sage/sage-9.5.beta9/local/include/fflas-ffpack/fflas/fflas_level3.inl:498:5:
>  
> error: no return statement in function returning non-void 
> [-Werror=return-type]
> > 498 | }
> > | ^
> >
> >
> > On Monday, December 27, 2021 at 11:51:24 AM UTC+1 dim...@gmail.com 
> wrote:
> >>
> >> On Mon, Dec 27, 2021 at 10:41 AM 'Florian Hanisch' via sage-devel
> >>  wrote:
> >> >
> >> > Hi,
> >> >
> >> > I have tried to compile sagemath 9.5beta9 on opensuse tumbleweed 
> (running on a DELL XPS 15, core i7, 16G RAM) but failed. I have been running
> >> >
> >> > ./configure --without-system-givaro
> >> > MAKE='make -j6' make
> >> >
> >> > Without the extra option "--without-system-givaro", linbox does not 
> build and the whole process quickly terminates. I also tried compiling 
> using gcc10 provided by my system but this did not resolve the issue.
> >> >
> >> > config.log is attached, install.log (approx 18MB) can be found here:
> >> >
> >> > https://baernextcloud.math.uni-potsdam.de/index.php/s/SJ9RRBxF6grrMoH
> >> >
> >> > I could not figure out what actually caused the problem, the end of 
> install.log reads
> >> >
> >> > [scipy-1.7.2] Successfully installed scipy-1.7.2
> >> > [scipy-1.7.2] Deleting temporary build directory
> >> > [scipy-1.7.2] 
> /home/fhanisch/programs/sage/sage-9.5.beta9/local/var/lib/sage/venv-python3.8/var/tmp/sage/build/scipy-1.7.2
> >> > [scipy-1.7.2] Finished installing scipy-1.7.2
> >> > make[2]: *** [Makefile:2389: all-start] Error 2
> >> > make[2]: Leaving directory 
> '/home/fhanisch/programs/sage/sage-9.5.beta9/build/make'
> >> >
> >> > real 47m33.472s
> >> > user 287m2.665s
> >> > sys 14m7.144s
> >> > ***
> >> > Error building Sage.
> >> >
> >> > The following package(s) may have failed to build (not necessarily
> >> > during this run of 'make all-start'):
> >> >
> >> probably the error is in building sagelib.
> >> Look in logs/pkgs/sagelib-9.5.beta9.log
> >>
> >> (you can also remove install.log and run make again, it will try (and
> >> most probably fail) at the point it failed the previous time)
> >>
> >>
> >>
> >> > It is safe to delete ...
> >> >
> >> > I hope that this googlegroup is the correct place to post the 
> problem, sorry for spamming if not. I am trying to compile the beta version 
> of sagemath 9.5 because compiling stable release 9.4 or lower failed, too. 
> I believe this is (at least partly) due to the "glibc >= 2.34" issue 
> described in https://wiki.sagemath.org/ReleaseTours/sage-9.4, so I 
> followed the recommendation mentioned there and went for 9.5beta9.
> >> >
> >> > T

Re: [sage-devel] sagemath 9.5beta9 fails to compile on opensuse tumbleweed

[Matthias Koeppe]

On Tuesday, December 28, 2021 at 5:32:51 AM UTC-8 Florian Hanisch wrote:

>  There was one interruption (sage-maxima.lisp not found while building the 
> docs). After adding the file to 
> /sage-9.5.beta9/local/var/lib/sage/venv-python3.8/lib64/python3.8/site-packages/sage/interfaces
>  
> and restarting the process, it seemed that compiling was successful. [...]
> However, the process actually did not build working binaries, ./sage only 
> yields an output of the form
>

I think you are running here into https://trac.sagemath.org/ticket/32868, 
which needs review

 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/7c161f07-d066-459a-a71d-11f07170c7fen%40googlegroups.com.

Re: [sage-devel] Docker images no longer being build and is gitlab still maintained?

[Matthias Koeppe]

I have opened https://trac.sagemath.org/ticket/33099 for this.

On Saturday, December 4, 2021 at 9:08:19 AM UTC-8 Dima Pasechnik wrote:

> One way or another, it's probably a good idea to run the builder on GH 
> Actions - translating one yml to another should be doable.
>
>
> On Sat, 4 Dec 2021, 16:11 julian...@fsfe.org,  wrote:
>
>> Hi Maarten,
>>
>> thanks for verifying that the Dockerfile still works.
>>
>> On Thursday, December 2, 2021 at 10:06:30 PM UTC-6 maarten...@navara.nl 
>> wrote:
>>
>>> In the meantime I managed to verify that aside from the gitlab CI/CD 
>>> there are no other things that are broken. Meaning that I managed to build 
>>> the docker file shipped with sage just fine on my laptop. I pushed a build 
>>> of 9.4 to https://hub.docker.com/r/mderickx/sagemath/ in case anyone is 
>>> interested.
>>>
>>
>> Did you also run the tests on the docker image? There are three tests 
>> defined here 
>> https://gitlab.com/sagemath/sage/-/blob/develop/.gitlab-ci.yml#L145. 
>> These often failed in the past with new releases.
>>
>> julian
>>
>> -- 
>>
> 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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/6d614b77-f673-4dbf-9e38-661fc7af4247n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a9374676-cfb6-43cf-a009-598130516d81n%40googlegroups.com.

[sage-devel] Re: venv changes require update to installation guide

[Matthias Koeppe]

I have opened https://trac.sagemath.org/ticket/33111 for this

On Sunday, January 2, 2022 at 9:59:17 AM UTC-8 Nils Bruin wrote:

> I just noticed that 9.5beta9 (perhaps earlier already?) requires changes 
> to the installation guide:
>
> In 
> https://doc.sagemath.org/html/en/installation/launching.html#setting-up-sagemath-as-a-jupyter-kernel-in-an-existing-jupyter-notebook-or-jupyterlab-installation
> some explicit paths are mentioned. These are now
>
> local/var/lib/sage/venv-python3.9.9/share/jupyter/kernels/sagemath/
>
> rather than (what they were before): local/share/jupyter/kernels/sagemath
>
> I suspect that with the venv-python3.9.9 labelling, this path will 
> continue to need updating, so perhaps an alternative way of figuring out 
> the appropriate path is preferred. 
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0be5e5c0-0929-47b8-a415-cd43ccfc1b6bn%40googlegroups.com.

[sage-devel] Proposal: Stop providing binary distributions

[Matthias Koeppe]

Comments/review please in https://trac.sagemath.org/ticket/33131

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/b22bfd03-bb75-452f-967d-c0e663b9ead2n%40googlegroups.com.

[sage-devel] GitPod

[Matthias Koeppe]

Thanks to work by Tobias Diez, we now have a fully functional GitPod 
(https://www.gitpod.io/) development environment for Sage in the cloud. 
GitPod runs Visual Studio Code (VS Code) in the web browser; but you can 
also connect it to VS Code running on the desktop.

To try out, see https://trac.sagemath.org/ticket/33103 (needs review).

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/797d2978-0128-45cb-876f-3dddf66fdd18n%40googlegroups.com.

Re: [sage-devel] Re: Proposal: Stop providing binary distributions

[Matthias Koeppe]

On Sunday, January 9, 2022 at 1:02:27 PM UTC-8 wst...@gmail.com wrote:

> Matthias, correct me if I'm wrong, but are you proposing that we just a
>
better job at pointing users to binary distributions of Sage such as 
> https://github.com/3-manifolds/Sage_macOS/releases, conda-forge, and 
> of course any packaging of Sage for Linux distros, etc., instead of 
> pointing them at binaries that don't work?


That's right, that's the proposal, see ticket 
https://trac.sagemath.org/ticket/33131 (needs review).

Instead of "Proposal: Stop providing binary distributions" maybe your 
> proposal is: 
>
> "Proposal: Group X will stop providing binary distributions, and instead 
> much more strongly encourage and advertise the work of groups 
> Y, Z, etc... to provide binary distributions" ?
>

where Group X =  the upstream project SageMath.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f02c840b-adfc-4740-8966-bf71d4474da9n%40googlegroups.com.

Re: [sage-devel] Re: Proposal: Stop providing binary distributions

[Matthias Koeppe]

On Monday, January 10, 2022 at 12:11:19 AM UTC-8 Dima Pasechnik wrote:

>
> On Mon, 10 Jan 2022, 01:31 Matthias Koeppe,  wrote:
>
>> On Sunday, January 9, 2022 at 1:02:27 PM UTC-8 wst...@gmail.com wrote:
>>
>>> Instead of "Proposal: Stop providing binary distributions" maybe your
>>>
>> proposal is: 
>>>
>>> "Proposal: Group X will stop providing binary distributions, and instead 
>>> much more strongly encourage and advertise the work of groups 
>>> Y, Z, etc... to provide binary distributions" ?
>>>
>>
>> where Group X =  the upstream project SageMath.
>>
>
> I suppose it should not include (binary) wheels (still very much WIP) and 
> docker or other VM-like images, right?
>

Agreed. See ticket (needs review).


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/75bba88b-2f0c-402a-8606-f0967ddb4fb3n%40googlegroups.com.

Re: [sage-devel] sagemath 9.5rc0 still not compiling on opensuse tumbleweed

[Matthias Koeppe]

See https://groups.google.com/g/sage-devel/c/81unMG60MyU/m/iDXLIDc0EAAJ - 
this comes in through the sysconfig of opensuse's python3.

This should be reported as a bug to opensuse. 


On Wednesday, January 12, 2022 at 5:48:04 AM UTC-8 Dima Pasechnik wrote:

> On Wed, Jan 12, 2022 at 1:35 PM Michael Orlitzky  
> wrote:
> >
> > On Wed, 2022-01-12 at 13:27 +, Dima Pasechnik wrote:
> > > > to see if it can be overridden. But it would be nice to track down 
> the
> > > > source of the -Werror so that it can be fixed for others.
> > >
> > > I have found it - it's absense of return statement in an inline
> > > function in an fflas-ffpack header,
> > > see my message for details.
> > >
> > >
> >
> > I mean, who adds the "-Werror=return-type" flag? That's bound to cause
> > other problems.
>
> Could be compiler configuration on that particular system, or on that
> particular OS, perhaps.
>
> >
> >
> > --
> > 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+...@googlegroups.com.
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/ba8ae322834fff41b0f7a86a2f877e6947ecb214.camel%40orlitzky.com
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/ac06b55c-90a4-44f3-aa0e-6c940f1a55a1n%40googlegroups.com.

Re: [sage-devel] sagemath 9.5rc0 still not compiling on opensuse tumbleweed

[Matthias Koeppe]

I have opened https://trac.sagemath.org/ticket/33153 for this.

On Wednesday, January 12, 2022 at 9:20:55 AM UTC-8 bae...@gmail.com wrote:

> Indeed, adding the flag 
> export CFLAGS="${CFLAGS} -Wno-error=return-type"
> fixed the problem. Never had to do this in the past though.
>
> Thanks a lot for the help!
>
> Michael Orlitzky schrieb am Mittwoch, 12. Januar 2022 um 14:18:20 UTC+1:
>
>> On Wed, 2022-01-12 at 10:19 +, Dima Pasechnik wrote: 
>> > 
>> > Basically, your C++ compiler is too strict. 
>>
>> I think it's just the CFLAGS that are too strict: 
>>
>> error: Command "gcc-10 -Wno-unused-result -Wsign-compare -DNDEBUG 
>> -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong 
>> -funwind-tables -fasynchronous-unwind-tables 
>> -fstack-clash-protection -Werror=return-type ... 
>>
>> If it wasn't added manually, that "-Werror=return-type" likely came 
>> from some pkg-config file and was automatically appended to CFLAGS. 
>> First I would try 
>>
>> export CFLAGS="${CFLAGS} -Wno-error=return-type" 
>> ./configure 
>> make 
>>
>> to see if it can be overridden. But it would be nice to track down the 
>> source of the -Werror so that it can be fixed for others. 
>>
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a94c79c8-266d-4b72-91fe-a3077f925708n%40googlegroups.com.

Re: [sage-devel] asking for setting up cythonizing compiling

[Matthias Koeppe]

On Monday, January 17, 2022 at 5:14:30 PM UTC-8 Michael Orlitzky wrote:

> Dark magic is relative, but for someone new [...]
>

(rant deleted)

1) "make build" just works
2) "./sage -b" just works.


 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d9545b7c-5c19-4226-afc4-55d53846581an%40googlegroups.com.

Re: [sage-devel] asking for setting up cythonizing compiling

[Matthias Koeppe]

On Monday, January 17, 2022 at 5:31:24 PM UTC-8 wst...@gmail.com wrote:

> Unfortunately, the
> "python setup.py develop"  workflow didn't even exist when we first 
> made "sage -b".  [...]
>

It exists now, it is called "pip install --editable" these days.

In the Sage distribution, you activate it for the Sage library by saying 
"./configure --enable-editable".
This has been available since Sage 9.3, thanks to the work by Tobias Diez.
See 
https://wiki.sagemath.org/ReleaseTours/sage-9.3#Editable_.28.22in-place.22.2C_.22develop.22.29_installs_of_the_Sage_library
 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/21942080-a7f0-4211-98d6-91c7d29bcd47n%40googlegroups.com.

Re: [sage-devel] Re: 32768

[Matthias Koeppe]

On Tuesday, January 18, 2022 at 7:54:19 AM UTC-8 wst...@gmail.com wrote:

> Who will solve ticket #32768 -- https://trac.sagemath.org/ticket/32768 
>
> "centos-7-i386: SIGFPE while building dochtml"

with no other information at all.


You can reproduce this failure by typing "tox -e 
docker-centos-7-i386-standard".

My on topic question (given the power of 2 discussion) is: 
>
> I'm curious -- what is the situation is with Sage and 32-bit Linux?


Supported, see list of platforms 
in https://wiki.sagemath.org/ReleaseTours/sage-9.5#Sources
as tested on each release tag on GH Actions. 



-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0fd7769f-fe6e-4d16-b5d2-59fb6164b6fdn%40googlegroups.com.

Re: [sage-devel] Re: 32768

[Matthias Koeppe]

On Tuesday, January 18, 2022 at 8:32:47 AM UTC-8 Matthias Koeppe wrote:

> On Tuesday, January 18, 2022 at 7:54:19 AM UTC-8 wst...@gmail.com wrote:
>
>> Who will solve ticket #32768 -- https://trac.sagemath.org/ticket/32768 
>>
>> "centos-7-i386: SIGFPE while building dochtml"
>
> with no other information at all.
>
>
> You can reproduce this failure by typing "tox -e 
> docker-centos-7-i386-standard".
>

... or use one of the containers built by the CI 
- https://github.com/mkoeppe?tab=packages&q=centos-7-i386

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0ec87e18-7c47-4a15-b32d-6a63f43d4ad9n%40googlegroups.com.

Re: [sage-devel] Re: 32768

[Matthias Koeppe]

On Tuesday, January 18, 2022 at 11:19:44 AM UTC-8 Thierry 
(sage-googlesucks@xxx) wrote:

> What seems clear to me is that [...] most 
> upstream projects seem not test fo 32bit architecture anymore.
>

Indeed many upstream projects have insufficient portability coverage even 
if they already use some CI. 

I have started to push some of our portability infrastructure upstream. See 
for example:

- 
https://github.com/linbox-team/fflas-ffpack/blob/master/.github/workflows/ci-sage.yml
- https://github.com/Normaliz/Normaliz/blob/master/.github/workflows/ci-sage.yml
- 
https://github.com/Singular/Singular/blob/spielwiese/.github/workflows/ci-sage.yml
- https://github.com/sympy/sympy/blob/master/.github/workflows/ci-sage.yml

I would recommend this approach when you run into portability issues with 
upstream projects.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/235e3468-0d2c-4f43-bf88-2609a9c7b201n%40googlegroups.com.

[sage-devel] Re: https://wiki.sagemath.org/ReleaseTours/sage-9.5

[Matthias Koeppe]

Any final additions to the Sage 9.5 release tour?
https://wiki.sagemath.org/ReleaseTours/sage-9.5


   1. Symbolics <https://wiki.sagemath.org/ReleaseTours/sage-9.5#Symbolics>
  1. Changes to symbolic expressions 
  
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Changes_to_symbolic_expressions>
  2. Interface to Mathics, a free implementation of the Wolfram language 
  
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Interface_to_Mathics.2C_a_free_implementation_of_the_Wolfram_language>
   2. Linear Algebra 
   <https://wiki.sagemath.org/ReleaseTours/sage-9.5#Linear_Algebra>
   3. Manifolds <https://wiki.sagemath.org/ReleaseTours/sage-9.5#Manifolds>
  1. De Rham cohomology and characteristic classes 
  
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#De_Rham_cohomology_and_characteristic_classes>
  2. Automatic coordinate change in curve plots 
  
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Automatic_coordinate_change_in_curve_plots>
  3. Internal code improvements and bug fixes 
  
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Internal_code_improvements_and_bug_fixes>
   4. Number theory 
   <https://wiki.sagemath.org/ReleaseTours/sage-9.5#Number_theory>
  1. Elliptic curves and isogenies 
  
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Elliptic_curves_and_isogenies>
  2. Modular and quasimodular forms 
  
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Modular_and_quasimodular_forms>
   5. Algebra <https://wiki.sagemath.org/ReleaseTours/sage-9.5#Algebra>
  1. New lazy Laurent series backend 
  
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#New_lazy_Laurent_series_backend>
  2. Lazy Dirichlet series 
  <https://wiki.sagemath.org/ReleaseTours/sage-9.5#Lazy_Dirichlet_series>
   6. Deprecated and removed functionality 
   
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Deprecated_and_removed_functionality>
   7. Package upgrades 
   <https://wiki.sagemath.org/ReleaseTours/sage-9.5#Package_upgrades>
   8. Configuration changes 
   <https://wiki.sagemath.org/ReleaseTours/sage-9.5#Configuration_changes>
  1. Separate virtual environment for Python packages 
  
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Separate_virtual_environment_for_Python_packages>
  2. New default: configure --with-system-gcc=force 
  
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#New_default:_configure_--with-system-gcc.3Dforce>
  3. New option: configure --disable-doc 
  
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#New_option:_configure_--disable-doc>
  4. Packages atlas and mpir removed 
  
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Packages_atlas_and_mpir_removed>
  5. psutil package removed 
  <https://wiki.sagemath.org/ReleaseTours/sage-9.5#psutil_package_removed>
   9. For developers and packagers: Modularization and packaging changes 
   
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#For_developers_and_packagers:_Modularization_and_packaging_changes>
  1. New distribution package on PyPI: sage-setup 
  
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#New_distribution_package_on_PyPI:_sage-setup>
  2. Pynac merged into the Sage library 
  
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Pynac_merged_into_the_Sage_library>
  3. Doctest annotation "# optional - FEATURE" for portions of the Sage 
  library 
  
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Doctest_annotation_.22.23_optional_-_FEATURE.22_for_portions_of_the_Sage_library>
  4. Module-level annotation "# sage.doctest: optional - FEATURE" 
  
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Module-level_annotation_.22.23_sage.doctest:_optional_-_FEATURE.22>
  5. Abstract base classes for "isinstance" testing 
  
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Abstract_base_classes_for_.22isinstance.22_testing>
   10. Availability of Sage 9.5 and installation help 
   
<https://wiki.sagemath.org/ReleaseTours/sage-9.5#Availability_of_Sage_9.5_and_installation_help>
  1. Sources <https://wiki.sagemath.org/ReleaseTours/sage-9.5#Sources>
  2. Binaries <https://wiki.sagemath.org/ReleaseTours/sage-9.5#Binaries>
  3. Help <https://wiki.sagemath.org/ReleaseTours/sage-9.5#Help>
   11. More details 
   <https://wiki.sagemath.org/ReleaseTours/sage-9.5#More_details>


On Tuesday, December 14, 2021 at 11:55:27 AM UTC-8 Matthias Koeppe wrote:

> On Tuesday, November 2, 2021 at 12:37:01 PM UTC-7 Matthias Koeppe wrote:
>
>> It's time to work on the release tour for Sage 9.5:
>> https://wiki.sagemath.org/ReleaseTours/sage-9.5
>> If you don't have an account that allows you to edit the wiki, please 
>&

Re: [sage-devel] Re: https://wiki.sagemath.org/ReleaseTours/sage-9.5

[Matthias Koeppe]

Yes, == and === is the wiki markup for sections

On Wednesday, January 19, 2022 at 10:41:56 AM UTC-8 Dima Pasechnik wrote:

> On Wed, Jan 19, 2022 at 6:36 PM Matthias Koeppe
>  wrote:
> >
> > You didn't add a section
>
> no idea what this means, to add a section. Is `== Number theory ==` a 
> section?
> What kind of magic is supposed to count the entries there?
>
> >
> > On Wednesday, January 19, 2022 at 10:30:14 AM UTC-8 Dima Pasechnik wrote:
> >>
> >> On Wed, Jan 19, 2022 at 5:24 PM Dima Pasechnik  
> wrote:
> >> >
> >> > Something about prinecount and related functions should be added. 
> I'll do this.
> >>
> >> OK, I've added a bit, but the TOC does not get updated, for some
> >> reason (Number theory should have 4 items, not 2).
> >>
> >> Dima
> >>
> >> >
> >> >
> >> > On Wed, 19 Jan 2022, 16:58 Matthias Koeppe,  
> wrote:
> >> >>
> >> >> Any final additions to the Sage 9.5 release tour?
> >> >> https://wiki.sagemath.org/ReleaseTours/sage-9.5
> >> >>
> >> >> Symbolics
> >> >>
> >> >> Changes to symbolic expressions
> >> >> Interface to Mathics, a free implementation of the Wolfram language
> >> >>
> >> >> Linear Algebra
> >> >> Manifolds
> >> >>
> >> >> De Rham cohomology and characteristic classes
> >> >> Automatic coordinate change in curve plots
> >> >> Internal code improvements and bug fixes
> >> >>
> >> >> Number theory
> >> >>
> >> >> Elliptic curves and isogenies
> >> >> Modular and quasimodular forms
> >> >>
> >> >> Algebra
> >> >>
> >> >> New lazy Laurent series backend
> >> >> Lazy Dirichlet series
> >> >>
> >> >> Deprecated and removed functionality
> >> >> Package upgrades
> >> >> Configuration changes
> >> >>
> >> >> Separate virtual environment for Python packages
> >> >> New default: configure --with-system-gcc=force
> >> >> New option: configure --disable-doc
> >> >> Packages atlas and mpir removed
> >> >> psutil package removed
> >> >>
> >> >> For developers and packagers: Modularization and packaging changes
> >> >>
> >> >> New distribution package on PyPI: sage-setup
> >> >> Pynac merged into the Sage library
> >> >> Doctest annotation "# optional - FEATURE" for portions of the Sage 
> library
> >> >> Module-level annotation "# sage.doctest: optional - FEATURE"
> >> >> Abstract base classes for "isinstance" testing
> >> >>
> >> >> Availability of Sage 9.5 and installation help
> >> >>
> >> >> Sources
> >> >> Binaries
> >> >> Help
> >> >>
> >> >> More details
> >> >>
> >> >>
> >> >> On Tuesday, December 14, 2021 at 11:55:27 AM UTC-8 Matthias Koeppe 
> wrote:
> >> >>>
> >> >>> On Tuesday, November 2, 2021 at 12:37:01 PM UTC-7 Matthias Koeppe 
> wrote:
> >> >>>>
> >> >>>> It's time to work on the release tour for Sage 9.5:
> >> >>>> https://wiki.sagemath.org/ReleaseTours/sage-9.5
> >> >>>> If you don't have an account that allows you to edit the wiki, 
> please feel free to just post additions as a reply here; I can add them to 
> the page.
> >> >>>
> >> >>>
> >> >>> So far we have:
> >> >>>
> >> >>> Contents
> >> >>>
> >> >>> Sage 9.5 Release Tour
> >> >>>
> >> >>> Symbolics
> >> >>>
> >> >>> Changes to symbolic expressions
> >> >>> Interface to Mathics, a free implementation of the Wolfram language
> >> >>>
> >> >>> Linear Algebra
> >> >>> Manifolds
> >> >>> Number theory
> >> >>>
> >> >>> Elliptic curves and isogenies
> >> >>> Modular and quasimodular forms
> >> >>>
> >> >>> Algebra
> >> >>>
> >> >>

Re: [sage-devel] Re: https://wiki.sagemath.org/ReleaseTours/sage-9.5

[Matthias Koeppe]

Check the link used for primecount 
<https://en.wikipedia.org/wiki/Moment_problem> please

On Wednesday, January 19, 2022 at 11:39:47 AM UTC-8 Dima Pasechnik wrote:

> OK,sorry, I looked in the wrong place. All fixed now.
>
> On Wed, Jan 19, 2022 at 7:34 PM Matthias Koeppe
>  wrote:
> >
> > You added 2 bullet points after the existing 2 bullet points at the top 
> of section 4 "Number Theory".
> > After the 4 bullet points, there are 2 subsections. These are what 
> appears in the TOC.
> >
> >
> >
> > On Wednesday, January 19, 2022 at 11:27:39 AM UTC-8 Dima Pasechnik wrote:
> >>
> >> On Wed, Jan 19, 2022 at 7:05 PM Matthias Koeppe
> >>  wrote:
> >> >
> >> > Which section are you missing?
> >> in the TOC there is
> >>
> >> 4. Number theory
> >> 1. Elliptic curves and isogenies
> >> 2. Modular and quasimodular forms
> >> 5. ...
> >>
> >> but it should be
> >>
> >> 4. Number theory
> >> 1. Elliptic curves and isogenies
> >> 2. Modular and quasimodular forms
> >> 3. (about binary forms)
> >> 4. (about prime_pi etc)
> >> 5. ...
> >>
> >> No idea how
> >>
> >> 1. Elliptic curves and isogenies
> >> 2. Modular and quasimodular forms
> >> got there in the TOC...
> >>
> >>
> >> >
> >> > On Wednesday, January 19, 2022 at 10:45:43 AM UTC-8 Dima Pasechnik 
> wrote:
> >> >>
> >> >> On Wed, Jan 19, 2022 at 6:43 PM Matthias Koeppe
> >> >>  wrote:
> >> >> >
> >> >> > Yes, == and === is the wiki markup for sections
> >> >>
> >> >> so the section is already there. Why does the TOC only list 2 
> entries there?
> >> >>
> >> >> >
> >> >> > On Wednesday, January 19, 2022 at 10:41:56 AM UTC-8 Dima Pasechnik 
> wrote:
> >> >> >>
> >> >> >> On Wed, Jan 19, 2022 at 6:36 PM Matthias Koeppe
> >> >> >>  wrote:
> >> >> >> >
> >> >> >> > You didn't add a section
> >> >> >>
> >> >> >> no idea what this means, to add a section. Is `== Number theory 
> ==` a section?
> >> >> >> What kind of magic is supposed to count the entries there?
> >> >> >>
> >> >> >> >
> >> >> >> > On Wednesday, January 19, 2022 at 10:30:14 AM UTC-8 Dima 
> Pasechnik wrote:
> >> >> >> >>
> >> >> >> >> On Wed, Jan 19, 2022 at 5:24 PM Dima Pasechnik <
> dim...@gmail.com> wrote:
> >> >> >> >> >
> >> >> >> >> > Something about prinecount and related functions should be 
> added. I'll do this.
> >> >> >> >>
> >> >> >> >> OK, I've added a bit, but the TOC does not get updated, for 
> some
> >> >> >> >> reason (Number theory should have 4 items, not 2).
> >> >> >> >>
> >> >> >> >> Dima
> >> >> >> >>
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > On Wed, 19 Jan 2022, 16:58 Matthias Koeppe, <
> matthia...@gmail.com> wrote:
> >> >> >> >> >>
> >> >> >> >> >> Any final additions to the Sage 9.5 release tour?
> >> >> >> >> >> https://wiki.sagemath.org/ReleaseTours/sage-9.5
> >> >> >> >> >>
> >> >> >> >> >> Symbolics
> >> >> >> >> >>
> >> >> >> >> >> Changes to symbolic expressions
> >> >> >> >> >> Interface to Mathics, a free implementation of the Wolfram 
> language
> >> >> >> >> >>
> >> >> >> >> >> Linear Algebra
> >> >> >> >> >> Manifolds
> >> >> >> >> >>
> >> >> >> >> >> De Rham cohomology and characteristic classes
> >> >> >> >> >> Automatic coordinate change in curve plots
> >> >> >> >> >> Internal code improvements and bug fixes
> >> >> >> >> >>
> >> >> >

[sage-devel] Patchbot/CI improvements

[Matthias Koeppe]

Patchbot experts:
1) Currently the patchbot does not run on certain tickets that make changes 
to build/pkgs, so we do not have automatic testing for these tickets. Is 
this something that can be changed? 
2) Can "make doc-pdf" please be added? 

I don't know if Volker's integration scripts look at the patchbot status at 
all, but nevertheless these two changes could improve our workflow.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/806c043e-e59f-4d89-8014-aafe3cd02efdn%40googlegroups.com.

Re: [sage-devel] Patchbot/CI improvements

[Matthias Koeppe]

Thanks, I've opened 
- https://github.com/sagemath/sage-patchbot/issues/148
- https://github.com/sagemath/sage-patchbot/issues/149

On Sunday, January 23, 2022 at 11:57:02 AM UTC-8 vdelecroix wrote:

> Le 23/01/2022 à 18:35, Matthias Koeppe a écrit :
> > Patchbot experts:
> > 1) Currently the patchbot does not run on certain tickets that make 
> changes
> > to build/pkgs, so we do not have automatic testing for these tickets. Is
> > this something that can be changed?
>
> I would say that this is doable (since if I remember correctly, packages
> can be downloaded from their upstream urls). Please open an issue on
> sage-patchbot.
>
> > 2) Can "make doc-pdf" please be added?
>
> It is (sort of) already there
>
>
> https://github.com/sagemath/sage-patchbot/blob/master/sage_patchbot/plugins.py#L179
>
> That could be activated by default if the experimental status of
> this plugin is removed. You can also open an issue.
>
> > I don't know if Volker's integration scripts look at the patchbot status 
> at
> > all, but nevertheless these two changes could improve our workflow.
> > 
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a233e685-245e-43d2-9b83-dea2ca0adeb5n%40googlegroups.com.

[sage-devel] Re: Patchbot/CI improvements

[Matthias Koeppe]

I have also prepared a PR for the "git releasemgr" scripts to make it 
easier to merge only tickets in the current milestone.
https://github.com/sagemath/git-trac-command/pull/54


On Sunday, January 23, 2022 at 9:35:54 AM UTC-8 Matthias Koeppe wrote:

> Patchbot experts:
> 1) Currently the patchbot does not run on certain tickets that make 
> changes to build/pkgs, so we do not have automatic testing for these 
> tickets. Is this something that can be changed? 
> 2) Can "make doc-pdf" please be added? 
>
> I don't know if Volker's integration scripts look at the patchbot status 
> at all, but nevertheless these two changes could improve our workflow.
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/22a29f74-f032-47c6-a526-8e20069f6d4an%40googlegroups.com.

[sage-devel] Re: Patchbot/CI improvements

[Matthias Koeppe]

And here is one so that on merge conflicts, there is no manual work for the 
release managers, and developers get some information about the conflict 
other than "merge conflict". 
https://github.com/sagemath/git-trac-command/pull/57

On Sunday, January 23, 2022 at 1:18:40 PM UTC-8 Matthias Koeppe wrote:

> I have also prepared a PR for the "git releasemgr" scripts to make it 
> easier to merge only tickets in the current milestone.
> https://github.com/sagemath/git-trac-command/pull/54
>
>
> On Sunday, January 23, 2022 at 9:35:54 AM UTC-8 Matthias Koeppe wrote:
>
>> Patchbot experts:
>> 1) Currently the patchbot does not run on certain tickets that make 
>> changes to build/pkgs, so we do not have automatic testing for these 
>> tickets. Is this something that can be changed? 
>> 2) Can "make doc-pdf" please be added? 
>>
>> I don't know if Volker's integration scripts look at the patchbot status 
>> at all, but nevertheless these two changes could improve our workflow.
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/dbd9c679-fc89-4dc9-a2f3-c5b2d0d06f06n%40googlegroups.com.

[sage-devel] Re: Patchbot/CI improvements

[Matthias Koeppe]

On Sunday, January 23, 2022 at 9:35:54 AM UTC-8 Matthias Koeppe wrote:

> I don't know if Volker's integration scripts look at the patchbot status 
> at all
>

Turns out they don't.

https://github.com/sagemath/git-trac-command/pull/58 fixes this

 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/fae7321b-004e-43ad-a7ae-b7069e96a2bdn%40googlegroups.com.

[sage-devel] https://github.com/sagemath/sagetrac-mirror is missing recent tags

[Matthias Koeppe]

https://github.com/sagemath/sagetrac-mirror/tags stops at 9.3.beta1 


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/4fd2ce7c-8df0-4e8c-867a-ea06060405cbn%40googlegroups.com.

[sage-devel] Re: Parallel docbuild

[Matthias Koeppe]

Yes, this was an unfortunate side-effect of the hotfix I made 
in https://trac.sagemath.org/ticket/33130
operating under the assumption that the 9.5 release would be imminent.

On Friday, January 28, 2022 at 2:01:32 AM UTC-8 Markus Wageringel wrote:

> Currently, the html docs are not built in parallel when running 
> `MAKE='make -j10' make ptestlong`, even when SAGE_NUM_THREADS is set. Is 
> there a way to enable it again? This also limits the throughput of the 
> patchbots.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0134750b-d345-4088-b1d3-92da65e33e90n%40googlegroups.com.

[sage-devel] Re: Parallel docbuild

[Matthias Koeppe]

I have opened https://trac.sagemath.org/ticket/33243 for this. Help is 
welcome.


On Friday, January 28, 2022 at 10:13:41 AM UTC-8 Matthias Koeppe wrote:

> Yes, this was an unfortunate side-effect of the hotfix I made in 
> https://trac.sagemath.org/ticket/33130
> operating under the assumption that the 9.5 release would be imminent.
>
> On Friday, January 28, 2022 at 2:01:32 AM UTC-8 Markus Wageringel wrote:
>
>> Currently, the html docs are not built in parallel when running 
>> `MAKE='make -j10' make ptestlong`, even when SAGE_NUM_THREADS is set. Is 
>> there a way to enable it again? This also limits the throughput of the 
>> patchbots.
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/3d054fb9-1796-4708-b103-49d4c904fb4fn%40googlegroups.com.

[sage-devel] Re: Parallel docbuild

[Matthias Koeppe]

A fix is now ready for testing

On Friday, January 28, 2022 at 11:17:21 AM UTC-8 Matthias Koeppe wrote:

> I have opened https://trac.sagemath.org/ticket/33243 for this. Help is 
> welcome.
>
>
> On Friday, January 28, 2022 at 10:13:41 AM UTC-8 Matthias Koeppe wrote:
>
>> Yes, this was an unfortunate side-effect of the hotfix I made in 
>> https://trac.sagemath.org/ticket/33130
>> operating under the assumption that the 9.5 release would be imminent.
>>
>> On Friday, January 28, 2022 at 2:01:32 AM UTC-8 Markus Wageringel wrote:
>>
>>> Currently, the html docs are not built in parallel when running 
>>> `MAKE='make -j10' make ptestlong`, even when SAGE_NUM_THREADS is set. Is 
>>> there a way to enable it again? This also limits the throughput of the 
>>> patchbots.
>>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d43fae4e-21df-4fbc-bdef-d550ba63f5den%40googlegroups.com.

Re: [sage-devel] Failure to build Sage 9.4 on Monterey

[Matthias Koeppe]

Hi Jeremy,
It depends on what you mean by "every day".
If today is included, there is no version that is both a "stable release" 
and supports the Apple M1.
If "every day" starts at on a day in the future when Sage 9.5 is released, 
then Sage 9.5 will satisfy your criteria.
More information on platform support of Sage versions 
- https://wiki.sagemath.org/ReleaseTours
Matthias

On Friday, January 28, 2022 at 5:34:59 PM UTC-8 jeremy@gmail.com wrote:

> Thanks, Dima.  I'm looking for a stable version to use every day, so I 
> guess I need to wait until the official release of 9.5?
>
> I'm no expert on reading install logs but the problem looks like it is 
> about a specific package.
>
> -Jeremy
>
>
> On 1/28/22 5:17 PM, Dima Pasechnik wrote:
>
>
>
> On Fri, 28 Jan 2022, 22:31 Jeremy Martin,  wrote:
>
>> Apologies if I'm missing something, but 9.4 appears to be the current 
>> version available on sagemath.org and all its mirrors.
>
>
> https://www.sagemath.org/download-latest.html
>
> -JLM
>>
>> On Friday, January 28, 2022 at 3:12:29 PM UTC-6 dim...@gmail.com wrote:
>>
>>> 9.4 is not known to run on M1. 
>>> Try the latest, 9.5.rc4, instead.
>>>
>>> On Fri, 28 Jan 2022, 19:03 Jeremy Martin,  wrote:
>>>
 I am on a brand-new Apple M1 running Monterey 12.0.1.  I just tried to 
 build Sage 9.4 from source.  After installing XCode, command-line tools, 
 Homebrew, I get the following (complete log files attached). 

 
 [gmp-6.2.0] configure: error: Oops, mp_limb_t is 64 bits, but the 
 assembler code
 [gmp-6.2.0] in this configuration expects 32 bits.
 [gmp-6.2.0] Error configuring GMP (with CFLAGS unset).
 [gmp-6.2.0] Consult 
 /Applications/sage-9.4/local/var/tmp/sage/build/gmp-6.2.0/src/config.log 
 for for details.
 [gmp-6.2.0]
 [gmp-6.2.0] real0m13.729s
 [gmp-6.2.0] user0m5.814s
 [gmp-6.2.0] sys0m4.358s
 [gmp-6.2.0] 
 
 [gmp-6.2.0] Error installing package gmp-6.2.0
 [gmp-6.2.0] 
 
 [gmp-6.2.0] Please email sage-devel (
 http://groups.google.com/group/sage-devel)
 [gmp-6.2.0] explaining the problem and including the log files
 [gmp-6.2.0]   /Applications/sage-9.4/logs/pkgs/gmp-6.2.0.log
 [gmp-6.2.0] and
 [gmp-6.2.0]   /Applications/sage-9.4/config.log
 [gmp-6.2.0] Describe your computer, operating system, etc.
 [gmp-6.2.0] If you want to try to fix the problem yourself, *don't* 
 just cd to
 [gmp-6.2.0] /Applications/sage-9.4/local/var/tmp/sage/build/gmp-6.2.0 
 and type 'make' or whatever is appropriate.
 [gmp-6.2.0] Instead, the following commands setup all environment 
 variables
 [gmp-6.2.0] correctly and load a subshell for you to debug the error:
 [gmp-6.2.0]   (cd 
 '/Applications/sage-9.4/local/var/tmp/sage/build/gmp-6.2.0' && 
 '/Applications/sage-9.4/sage' --buildsh)
 [gmp-6.2.0] When you are done debugging, you can type "exit" to leave 
 the subshell.
 [gmp-6.2.0] 
 
 make[4]: *** [gmp-SAGE_LOCAL-no-deps] Error 1
 make[3]: *** 
 [/Applications/sage-9.4/local/var/lib/sage/installed/gmp-6.2.0] Error 2
 make[2]: *** [toolchain-deps] Error 2

 real0m44.133s
 user0m18.589s
 sys0m14.489s
 ***
 Error building Sage.

 The following package(s) may have failed to build (not necessarily
 during this run of 'make all-start'):

 * package: gmp-6.2.0
   last build time: Jan 28 12:11
   log file:/Applications/sage-9.4/logs/pkgs/gmp-6.2.0.log
   build directory: 
 /Applications/sage-9.4/local/var/tmp/sage/build/gmp-6.2.0

 It is safe to delete any log files and build directories, but they
 contain information that is helpful for debugging build problems.
 WARNING: If you now run 'make' again, the build directory of the
 same version of the package will, by default, be deleted. Set the
 environment variable SAGE_KEEP_BUILT_SPKGS=yes to prevent this.

 make[1]: *** [all-start] Error 1
 make: *** [all] Error 2

>>> -- 
 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+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/sage-devel/cd3795e6-775e-4603-a5d4-b51b0034e8fcn%40googlegroups.com
  
 
 .

>>> -- 
>> You received this message

[sage-devel] Sage and the Pyjion JIT compiler

[Matthias Koeppe]

We may be able to speed up the parts of Sage that are implemented in Python 
using the Pyjion JIT compiler (https://www.trypyjion.com/). Running the 
Sage test suite with  Pyjion activated works remarkably well; there are 
only a small number of crashes and test failures. I haven't checked whether 
there are any actual speedups for Sage code.
https://trac.sagemath.org/ticket/32845

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/88bd10d8-14fc-4882-ba1a-6bab8d1cbd4cn%40googlegroups.com.

[sage-devel] Re: https://wiki.sagemath.org/ReleaseTours/sage-9.5

[Matthias Koeppe]

Now that the updated Sage documentation is online at 
https://doc.sagemath.org/html/en/index.html (thanks, Harald!), we can add 
links to the reference manual.

On Tuesday, November 2, 2021 at 12:37:01 PM UTC-7 Matthias Koeppe wrote:

> It's time to work on the release tour for Sage 9.5:
> https://wiki.sagemath.org/ReleaseTours/sage-9.5
> If you don't have an account that allows you to edit the wiki, please feel 
> free to just post additions as a reply here; I can add them to the page.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/47eb65fd-8ad7-49b4-8902-ff1f53ddc541n%40googlegroups.com.

[sage-devel] Re: docbuild aborting on warnings

[Matthias Koeppe]

+1 on this as a new default if we add a flag for the current strict 
behavior, for use by Release Manager, patchbot, and GH Actions.

On Tuesday, February 1, 2022 at 12:06:15 PM UTC-8 Antonio Rojas wrote:

> Sage doc build currently aborts by default whenever sphinx emits a 
> warning, and keeps a hardcoded whitelist of "admissible" warnings that 
> needs to be kept up to date. This is very inconvenient for distros building 
> Sage with system Sphinx, as every new version introduces new warnings: a 
> fix was just committed for Sphinx 4.3 and now it is broken again with 4.4 
> due to new warnings.
>
> This is equivalent to adding "-Werror" in C/C++ build flags of released 
> software, which is widely regarded as bad practice, as there is a high 
> change of breakage when updating the compiler. Can we please reconsider 
> this policy? Fixing the warnings can still be a requirement for accepting 
> tickets upgrading Sage's bundled Sphinx, but this would make things less 
> painful for distributions.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/c8e52444-1a1b-463b-a2f0-af77917dee1dn%40googlegroups.com.

[sage-devel] Re: sage 9.5 build failed at package numpy-1.21.4 (on Windows Server 2019 WSL)

[Matthias Koeppe]

The compilation fails with a failed system call:

  /usr/include/x86_64-linux-gnu/bits/types.h:142:10: fatal error: 
/mnt/g/Maths/sage-9.5/clone/local/var/lib/sage/venv-python3.8/include/bits/time64.h:
 
Invalid argument
142 | #include  /* Defines __TIME*_T_TYPE macros.  */
|  ^~~
  compilation terminated.
 
This is likely sporadic and will go away if you just restart "make".
Tracked at https://trac.sagemath.org/ticket/31088



On Thursday, February 3, 2022 at 1:22:11 AM UTC-8 hohoa...@gmail.com wrote:

> Greetings,
>
> The instructions at  https://sagemanifolds.obspm.fr/install_ubuntu.html 
> were followed.
>
> It is much appreciated if someone would kindly point out what was missing 
> in the build process.
>
> Please find attached 'install.log.7z' and 'numpy-1.21.4.log.7z'
>
> Regards,
>
> phiho
>
> P.S: 
> $ uname -a
> Linux 4.4.0-17763-Microsoft #2268-Microsoft Thu Oct 07 16:36:00 PST 2021 
> x86_64 x86_64 x86_64 GNU/Linux
>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/461e60bb-5ae8-453c-b332-2bf2b02d6e14n%40googlegroups.com.

Re: [sage-devel] Re: sage 9.5 build failed at package numpy-1.21.4 (on Windows Server 2019 WSL)

[Matthias Koeppe]

It would probably be a good idea to do "make ccache" and then re-attempt 
the build. 
On Thursday, February 3, 2022 at 11:32:32 AM UTC-8 hohoa...@gmail.com wrote:

> Hi,
>
> Actually this approach was tried a few times before. The report was from a 
> fresh clone and build.
>
> 'MAKE="make -j8" make' was just tried again and the re-make ended 
> with these failed  packages:
>
> 
> real 13m20.842s
> user 14m38.391s
> sys 6m4.781s
> ***
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-start'):
>
> * package: arb-2.19.0.p0
>   last build time: Feb 3 12:08
>   log file:/mnt/g/Maths/sage-9.5/clone/logs/pkgs/arb-2.19.0.p0.log
>
> * package: pplpy-0.8.6
>   last build time: Feb 3 12:09
>   log file:/mnt/g/Maths/sage-9.5/clone/logs/pkgs/pplpy-0.8.6.log
>
> * package: sphinx-4.2.0
>   last build time: Feb 3 12:09
>   log file:/mnt/g/Maths/sage-9.5/clone/logs/pkgs/sphinx-4.2.0.log
>
> * package: numpy-1.21.4
>   last build time: Feb 3 12:13
>   log file:/mnt/g/Maths/sage-9.5/clone/logs/pkgs/numpy-1.21.4.log
>
> It is safe to delete any log files and build directories, but they
> contain information that is helpful for debugging build problems.
> WARNING: If you now run 'make' again, the build directory of the
> same version of the package will, by default, be deleted. Set the
> environment variable SAGE_KEEP_BUILT_SPKGS=yes to prevent this.
>
> 
>
> Please find attached 'config.log.7z' and the logs of failed packages* 
> including numpy-1.21.4*.log2.7z.
>
> FWIW, 'sage-9.4' was successfully built (the first time) from the tarball 
> (with 'configure' pre-made, downloaded from github) on this same machine 
> about a week ago.
> (The tarball for 'sage-9.5' did not go far)
>
> numpy-1.21.4 still failed in another re-make
>
> Regards,
>
> phiho
>
> P.S: I will be out of town and will have no access to the Internet (a 
> couple weeks or so), please allow me to catch up later on.
>
>
> On Thu, Feb 3, 2022 at 11:20 AM Matthias Koeppe  
> wrote:
>
>> The compilation fails with a failed system call:
>>
>>   /usr/include/x86_64-linux-gnu/bits/types.h:142:10: fatal error: 
>> /mnt/g/Maths/sage-9.5/clone/local/var/lib/sage/venv-python3.8/include/bits/time64.h:
>>  
>> Invalid argument
>> 142 | #include  /* Defines __TIME*_T_TYPE macros.  */
>> |  ^~~
>>   compilation terminated.
>>  
>> This is likely sporadic and will go away if you just restart "make".
>> Tracked at https://trac.sagemath.org/ticket/31088
>>
>>
>>
>> On Thursday, February 3, 2022 at 1:22:11 AM UTC-8 hohoa...@gmail.com 
>> wrote:
>>
>>> Greetings,
>>>
>>> The instructions at  https://sagemanifolds.obspm.fr/install_ubuntu.html 
>>> were followed.
>>>
>>> It is much appreciated if someone would kindly point out what was 
>>> missing in the build process.
>>>
>>> Please find attached 'install.log.7z' and 'numpy-1.21.4.log.7z'
>>>
>>> Regards,
>>>
>>> phiho
>>>
>>> P.S: 
>>> $ uname -a
>>> Linux 4.4.0-17763-Microsoft #2268-Microsoft Thu Oct 07 16:36:00 PST 2021 
>>> x86_64 x86_64 x86_64 GNU/Linux
>>>
>>>
>>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/461e60bb-5ae8-453c-b332-2bf2b02d6e14n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/sage-devel/461e60bb-5ae8-453c-b332-2bf2b02d6e14n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/751fde85-2d70-4fad-9f5a-05114f670b74n%40googlegroups.com.

[sage-devel] Re: minimal requirements

[Matthias Koeppe]

README.md links to the files build/pkgs/*_prereq*/distros/*.txt for this 
purpose.

Yes, the installation guide needs improvements; this is 
https://trac.sagemath.org/ticket/33088
(which needs help).




On Thursday, February 3, 2022 at 2:51:44 PM UTC-8 Thierry 
(sage-googlesucks@xxx) wrote:

> Hi,
>
> the install from source documentation used to separate between minimal
> requirements to build Sage and the optional packages that avoids
> building things that can be provided by the distro. It seems that the
> two list have been merged on recent documentation:
>
> https://doc.sagemath.org/html/en/installation/source.html
>
> Is there a place where we could find publically (not in
> SAGE_ROOT/build/pkgs/_prereq) the very minimal requirements to build
> Sage on some distros ?
>
> Ciao,
> Thierry
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/b14f1471-3a25-4db2-9816-f3070171b86bn%40googlegroups.com.

[sage-devel] Re: minimal requirements

[Matthias Koeppe]

And https://doc.sagemath.org/html/en/reference/spkg/_prereq.html#spkg-prereq 
has formatted versions of this information.

On Thursday, February 3, 2022 at 3:59:00 PM UTC-8 Matthias Koeppe wrote:

> README.md links to the files build/pkgs/*_prereq*/distros/*.txt for this 
> purpose.
>
> Yes, the installation guide needs improvements; this is 
> https://trac.sagemath.org/ticket/33088
> (which needs help).
>
>
>
>
> On Thursday, February 3, 2022 at 2:51:44 PM UTC-8 Thierry 
> (sage-googlesucks@xxx) wrote:
>
>> Hi,
>>
>> the install from source documentation used to separate between minimal
>> requirements to build Sage and the optional packages that avoids
>> building things that can be provided by the distro. It seems that the
>> two list have been merged on recent documentation:
>>
>> https://doc.sagemath.org/html/en/installation/source.html
>>
>> Is there a place where we could find publically (not in
>> SAGE_ROOT/build/pkgs/_prereq) the very minimal requirements to build
>> Sage on some distros ?
>>
>> Ciao,
>> Thierry
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/9a596a48-d080-465c-bad3-73134ce05531n%40googlegroups.com.

[sage-devel] Re: minimal requirements

[Matthias Koeppe]

On Friday, February 4, 2022 at 5:39:46 AM UTC-8 Eric Gourgoulhon wrote:

> Le vendredi 4 février 2022 à 01:05:05 UTC+1, Matthias Koeppe a écrit :
>
>> And 
>> https://doc.sagemath.org/html/en/reference/spkg/_prereq.html#spkg-prereq 
>> has formatted versions of this information.
>>
>
> Shouldn't gfortran be added to the above lists (at least for Linux 
> systems)? Of course, it is not strictly necessary, given that Sage can 
> build its own. However,  since we are requiring system g++, it would make 
> sense to demand system gfortran as well. In addition, this makes the build 
> faster.
>

This is true for all packages that we can accept from the system, which is 
why we recommend that users follow the recommendations that the configure 
script issues.
 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/ccd1a20a-fb58-44c6-a995-6cbec394a41cn%40googlegroups.com.

[sage-devel] Patchbot on GitHub Actions

[Matthias Koeppe]

It is now possible to run the Sage Patchbot in a container on GitHub 
Actions.

Go to https://github.com/sagemath/sage-patchbot, use the Fork button to 
create a fork in your account.

Go to the Actions tab,  select "Run patchbot". Push "Run workflow".
Instead of the default platform, ubuntu-focal-standard, you can select any 
platform for which we have prebuilt images:, 
see 
https://github.com/orgs/sagemath/packages?tab=packages&q=with-targets-optional
It will run for 6 hours, then exit. You can run multiple workflows 
simultaneously.



-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8cb13f3b-a8ed-4788-ae0e-4fe6943a6a73n%40googlegroups.com.

Re: [sage-devel] Building Sage 9.5 on macOS fails due to flint

[Matthias Koeppe]

Yes, you can clear out /usr/local and start the build from scratch.


On Monday, February 7, 2022 at 4:05:49 AM UTC-8 modp...@gmail.com wrote:

> So any ideas how to solve this without installing gmp and flint from 
> Homebrew? As I have already manually compiled and built them in my machine.
>
> On Friday, February 4, 2022 at 9:37:40 PM UTC+1 modp...@gmail.com wrote:
>
>> I actually had both gmp and flint manually installed before. Can I tell 
>> Sage somehow to use my local gmp and flint?
>> I had already issued: 
>> source .homebrew-build-env
>> However, I didn't issue ./bootstrap before doing ./configure.
>>
>> On Friday, February 4, 2022 at 7:27:40 PM UTC+1 dim...@gmail.com wrote:
>>
>>> Try using flint from Homebrew instead: 
>>>
>>> brew install flint 
>>>
>>> (by the way, it seems that your gmp Homebrew installation is broken - 
>>> maybe try reinstalling it, from Homebrew?) 
>>> And don't forget executing 
>>>
>>> source .homebrew-build-env 
>>>
>>> before 
>>> ./bootstrap && ./configure 
>>>
>>>
>>> On Fri, Feb 4, 2022 at 6:14 PM modp...@gmail.com  
>>> wrote: 
>>> > 
>>> > I'm building Sage 9.5 from source on macOS Monterey 12.2, however, it 
>>> fails when installing flint. I attach here the top level config and log 
>>> file for flint. Any ideas what the issue might be? 
>>> > 
>>> > 
>>> > -- 
>>> > 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+...@googlegroups.com. 
>>> > To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-devel/fba7b5fc-b0a2-42e4-b218-8be4e8aca141n%40googlegroups.com.
>>>  
>>>
>>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/7c9ac4ed-f32c-4982-90b7-8f284fa2b5efn%40googlegroups.com.

Re: [sage-devel] Can we restore `mean`?

[Matthias Koeppe]

IMO the best long-term solution is to make sure that the built-in stats 
module (https://docs.python.org/3/library/statistics.html) can be used. 
However, as explained in the ticket https://trac.sagemath.org/ticket/29662 
(and https://trac.sagemath.org/ticket/28234), there are bugs that prevent 
users from using it with some Sage types. 


On Saturday, February 12, 2022 at 7:28:43 PM UTC-8 wst...@gmail.com wrote:

> This happened in https://trac.sagemath.org/ticket/29662, as requested
> by kcrisman. I just looked at that
> ticket and added a comment about several additional examples where
> deprecating mean breaks things
> in subtle ways...
>
> On Sat, Feb 12, 2022 at 7:14 PM Samuel Lelievre
>  wrote:
> >
> > Dear sage-devel,
> >
> > Taking averages is a common operation, and a `mean` function
> > such that `mean(xx)` returns `sum(xx) / len(xx)` regardless of
> > the type of objects in the iterable `xx` is extremely convenient.
> >
> > For instance, for a polygon whose vertices `uu` have coordinates
> > in a number field and are represented as vectors over that field,
> > `mean(uu)` finds the centre of that polygon. To center the polygon
> > at the origin, use `c = mean(uu)` and `vv = [u - c for u in uu]`.
> >
> > In Sage 9.5, using `mean` displays a warning:
> > ```
> > DeprecationWarning: sage.stats.basic_stats.mean is deprecated;
> > use numpy.mean or numpy.nanmean instead
> > ```
> > This is after #29662 was merged in SageMath 9.5.beta1.
> >
> > Alas, `numpy.mean` cannot find the mean of a list of vectors
> > over a number field.
> >
> > Of course, as a workaround, I can define
> >
> > def mean(xx):
> > r"""
> > Return the mean of this iterable.
> > """
> > return sum(xx) / len(xx)
> >
> > and place that in an `init.sage` file in my `~/.sage` folder.
> >
> > Having that built into Sage is so much more convenient though.
> > Can we have it back?
> >
> > Kind polygonal regards, --Samuel
> >
> > --
> > 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+...@googlegroups.com.
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/60fe4b1c-db88-4caa-8d13-670b9b3edb79n%40googlegroups.com
> .
>
>
>
> -- 
> William (http://wstein.org)
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/72970d04-877d-41bb-8af5-7dce382f887bn%40googlegroups.com.

Re: [sage-devel] Can we restore `mean`?

[Matthias Koeppe]

On Sunday, February 13, 2022 at 12:58:41 PM UTC-8 David Roe wrote:

> The documentation of Python's statistics module notes that "Unless 
> explicitly noted, these functions support int, float, Decimal and Fraction. 
> Behaviour with other types (whether in the numeric tower or not) is 
> currently unsupported. Collections with a mix of types are also undefined 
> and implementation-dependent."
>

Yes, they need the Sage community's input to develop this further.
 

 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/809e1d38-c377-4bcc-a29f-b17b310437bcn%40googlegroups.com.

[sage-devel] Re: New trac status badges

[Matthias Koeppe]

Thanks a lot for this work, Tobias! Glad to see that it is merged now.

I have added a bit based on your posting 
to https://wiki.sagemath.org/ReleaseTours/sage-9.6


On Sunday, February 13, 2022 at 1:26:06 PM UTC-8 tobias...@gmail.com wrote:

> Hi everyone,
>
> as you probably have already seen, there are a few new status badges in 
> the trac ticket display.
> We have now:
> 1. Linter that checks that the code of the current branch adheres to the 
> style guidelines. In order to see details when it fails, you can click on 
> it and then select the most recent workflow run. (This already exists for a 
> while)
> 2. Buid & test that builds sage for the current branch (incrementally on 
> top of the system packages of the develop branch) and runs the test. 
> Details are again available by clicking on the badge. (This is currently 
> still gray until https://trac.sagemath.org/ticket/33263 is merged into 
> master)
> 3. Build documentation workflow that builds the documentation for the 
> current branch. If you click on it, you get the html output of the 
> successful run. The idea is to use this to easily inspect changes to the 
> documentation without the need to locally rebuild the docs yourself. If the 
> doc build fails, you can go to 
> https://github.com/sagemath/sagetrac-mirror/actions/workflows/doc-build.yml 
> and choose the particular branch to see what went wrong.
> 4. Open in gitpod. This will spin up a pre-configured dev environment in 
> the browser (based on VS code), where the branch is already checked-out and 
> everything is pre-build. Feel free to use it to quickly check that the 
> changes in the ticket work as expected or to even make further changes 
> yourself. To find out more: https://www.gitpod.io/
>
> The idea is that these three status badges complement the existing 
> patchbots (and maybe even replace them in the future). In particular, they 
> are supposed to always be green. Please keep this in mind when reviewing a 
> ticket. 
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/fa011350-6b93-40e2-948d-a88bce053c35n%40googlegroups.com.

Re: [sage-devel] Re: New trac status badges

[Matthias Koeppe]

Ticket for gitpod usability 
improvements: https://trac.sagemath.org/ticket/33113


On Monday, February 14, 2022 at 2:01:29 AM UTC-8 Dima Pasechnik wrote:

> Hi,
> I'm testing this on a ticket, and noticed that the Ubuntu host it runs
> on has Linuxbrew installed.
>
> gitpod /workspace/sagetrac-mirror (public/build/github_build) $ which brew
> /home/linuxbrew/.linuxbrew/bin/brew
> As a result, ./configure thinks it's a Homebrew macOS system...
> (This is e.g. trac 32753 - not worked on yet)
>
> Perhaps, if possible, not having Linuxbrew on the host might be a good
> idea, for the time being.
>
> Dima
>
> On Mon, Feb 14, 2022 at 12:15 AM Matthias Koeppe
>  wrote:
> >
> > Thanks a lot for this work, Tobias! Glad to see that it is merged now.
> >
> > I have added a bit based on your posting to 
> https://wiki.sagemath.org/ReleaseTours/sage-9.6
> >
> >
> > On Sunday, February 13, 2022 at 1:26:06 PM UTC-8 tobias...@gmail.com 
> wrote:
> >>
> >> Hi everyone,
> >>
> >> as you probably have already seen, there are a few new status badges in 
> the trac ticket display.
> >> We have now:
> >> 1. Linter that checks that the code of the current branch adheres to 
> the style guidelines. In order to see details when it fails, you can click 
> on it and then select the most recent workflow run. (This already exists 
> for a while)
> >> 2. Buid & test that builds sage for the current branch (incrementally 
> on top of the system packages of the develop branch) and runs the test. 
> Details are again available by clicking on the badge. (This is currently 
> still gray until https://trac.sagemath.org/ticket/33263 is merged into 
> master)
> >> 3. Build documentation workflow that builds the documentation for the 
> current branch. If you click on it, you get the html output of the 
> successful run. The idea is to use this to easily inspect changes to the 
> documentation without the need to locally rebuild the docs yourself. If the 
> doc build fails, you can go to 
> https://github.com/sagemath/sagetrac-mirror/actions/workflows/doc-build.yml 
> and choose the particular branch to see what went wrong.
> >> 4. Open in gitpod. This will spin up a pre-configured dev environment 
> in the browser (based on VS code), where the branch is already checked-out 
> and everything is pre-build. Feel free to use it to quickly check that the 
> changes in the ticket work as expected or to even make further changes 
> yourself. To find out more: https://www.gitpod.io/
> >>
> >> The idea is that these three status badges complement the existing 
> patchbots (and maybe even replace them in the future). In particular, they 
> are supposed to always be green. Please keep this in mind when reviewing a 
> ticket.
> >
> > --
> > 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+...@googlegroups.com.
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/fa011350-6b93-40e2-948d-a88bce053c35n%40googlegroups.com
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f131fbdb-4af2-498a-8ef6-04233b0e4370n%40googlegroups.com.

Re: [sage-devel] Re: sage 9.5 build failed at package numpy-1.21.4 (on Windows Server 2019 WSL)

[Matthias Koeppe]

I would suggest to try whether the "Invalid argument" syscall errors go 
away if you clone the Sage source tree in the Linux file system, for 
example, in "/sage", instead of a location mounted from the Windows file 
system (/mnt/g/Maths/sage-9.5/clone/).




On Tuesday, February 15, 2022 at 12:14:30 AM UTC-8 hohoa...@gmail.com wrote:

> Hi,
>
> Thank you so much for your advice.
>
> I just started afresh with a new clone from github and following the 
> instructions from https://sagemanifolds.obspm.fr/install_ubuntu.html
>
> After running './configure', conda was deactivated (twice):
>
> $ which conda
> /home/hph/miniconda3/bin/conda
>
> $ conda deactivate
> $ conda deactivate
>
> Then:
>
> $ make ccache
> $ MAKE="make -j8" make
>
> after 10 times of -re-make (with MAKE="make -j8"):
>
> $ ls -l *.log | wc -l
> 152
>
> $ ls -l *.log.error | wc -l
> 12
>
> All the errors from the earlier make's seemed to be fixed eventually in 
> the later re-make, all except 'scipy-1.7.2' and 'sagelib-9.5'
>
> Please find attached 'config.log.7z' and 'Error building a wheel for 
> scipy-1.7.2 - scipy-1.7.2.log.error.7z' (from re-make #5 to #10) and 
> 'sagelib-9.5.log.error.7z'
>
> The re-make #10, scipy-1.7.2 failed with:
>
> *error: Command "gfortran -Wall -g -ffixed-form -fno-second-underscore -g 
> -O2 -fPIC -fPIC -O3 -funroll-loops 
> -I/mnt/g/Maths/sage-9.5/clone/local/var/lib/sage/venv-python3.8/lib/python3.8/site-packages/numpy/core/include
>  
> -Ibuild/src.linux-x86_64-3.8/numpy/distutils/include -c -c 
> scipy/interpolate/fitpack/curev.f -o 
> build/temp.linux-x86_64-3.8/scipy/interpolate/fitpack/curev.o" failed with 
> exit status 1*
>
>   ### CLIB COMPILER OPTIMIZATION ###
>   Platform  :
> Architecture: x64
> Compiler: gcc
>
>   CPU baseline  :
> Requested   : 'min'
> Enabled : SSE SSE2 SSE3
> Flags   : -msse -msse2 -msse3
> Extra checks: none
>
>   CPU dispatch  :
> Requested   : 'max -xop -fma4'
> Enabled : SSSE3 SSE41 POPCNT SSE42 AVX F16C FMA3 AVX2 AVX512F 
> AVX512CD AVX512_KNL AVX512_KNM AVX512_SKX AVX512_CLX AVX512_CNL AVX512_ICL
> Generated   : none
>   CCompilerOpt.cache_flush[809] : write cache to path -> 
> /mnt/g/Maths/sage-9.5/clone/local/var/lib/sage/venv-python3.8/var/tmp/sage/build/scipy-1.7.2/src/build/temp.linux-x86_64-3.8/ccompiler_opt_cache_clib.py
>   *error: Command "gfortran -Wall -g -ffixed-form -fno-second-underscore 
> -g -O2 -fPIC -fPIC -O3 -funroll-loops 
> -I/mnt/g/Maths/sage-9.5/clone/local/var/lib/sage/venv-python3.8/lib/python3.8/site-packages/numpy/core/include
>  
> -Ibuild/src.linux-x86_64-3.8/numpy/distutils/include -c -c 
> scipy/interpolate/fitpack/curev.f -o 
> build/temp.linux-x86_64-3.8/scipy/interpolate/fitpack/curev.o" failed with 
> exit status 1*
>   Building wheel for scipy (pyproject.toml): finished with status 'error'
>   ERROR: Failed building wheel for scipy
> Failed to build scipy
> ERROR: Failed to build one or more wheels
>
> 
> Error building a wheel for scipy-1.7.2
>
> 
>
> real 3m25.289s
> user 6m14.359s
> sys 1m47.406s
>
> In the re-make #12, 'sagelib-9.5' build failed with:
> *error: [Errno 22] Invalid argument: 'sage/rings/power_series_poly.pxd'*
>
> Discovering Python/Cython source code
> distributions = ['']
> Discovered Python/Cython sources, time: 2.99 seconds.
> running build
> Generating auto-generated sources
> Building interpreters for fast_callable
> running build_cython
> Enabling Cython debugging support
> *error: [Errno 22] Invalid argument: 'sage/rings/power_series_poly.pxd'*
>
> real 0m17.411s
> user 0m4.844s
> sys 0m11.797s
>
>
> Regards,
>
> phiho
>
>
> On Thu, Feb 3, 2022 at 2:36 PM Matthias Koeppe  
> wrote:
>
>> It would probably be a good idea to do "make ccache" and then re-attempt 
>> the build. 
>> On Thursday, February 3, 2022 at 11:32:32 AM UTC-8 hohoa...@gmail.com 
>> wrote:
>>
>>> Hi,
>>>
>>> Actually this approach was tried a few times before. The report was from 
>>> a fresh clone and build.
>>>
>>> 'MAKE="make -j8" make' was just tried again and the re-make ended 
>>> with these failed  packages:
>>>
>>> 
>>> real 13m2

Re: [sage-devel] Re: sage 9.5 build failed at package numpy-1.21.4 (on Windows Server 2019 WSL)

[Matthias Koeppe]

(Is G: a network drive by any chance?)

On Tuesday, February 15, 2022 at 8:46:41 AM UTC-8 Matthias Koeppe wrote:

> I would suggest to try whether the "Invalid argument" syscall errors go 
> away if you clone the Sage source tree in the Linux file system, for 
> example, in "/sage", instead of a location mounted from the Windows file 
> system (/mnt/g/Maths/sage-9.5/clone/).
>
>
>
>
> On Tuesday, February 15, 2022 at 12:14:30 AM UTC-8 hohoa...@gmail.com 
> wrote:
>
>> Hi,
>>
>> Thank you so much for your advice.
>>
>> I just started afresh with a new clone from github and following the 
>> instructions from https://sagemanifolds.obspm.fr/install_ubuntu.html
>>
>> After running './configure', conda was deactivated (twice):
>>
>> $ which conda
>> /home/hph/miniconda3/bin/conda
>>
>> $ conda deactivate
>> $ conda deactivate
>>
>> Then:
>>
>> $ make ccache
>> $ MAKE="make -j8" make
>>
>> after 10 times of -re-make (with MAKE="make -j8"):
>>
>> $ ls -l *.log | wc -l
>> 152
>>
>> $ ls -l *.log.error | wc -l
>> 12
>>
>> All the errors from the earlier make's seemed to be fixed eventually in 
>> the later re-make, all except 'scipy-1.7.2' and 'sagelib-9.5'
>>
>> Please find attached 'config.log.7z' and 'Error building a wheel for 
>> scipy-1.7.2 - scipy-1.7.2.log.error.7z' (from re-make #5 to #10) and 
>> 'sagelib-9.5.log.error.7z'
>>
>> The re-make #10, scipy-1.7.2 failed with:
>>
>> *error: Command "gfortran -Wall -g -ffixed-form -fno-second-underscore -g 
>> -O2 -fPIC -fPIC -O3 -funroll-loops 
>> -I/mnt/g/Maths/sage-9.5/clone/local/var/lib/sage/venv-python3.8/lib/python3.8/site-packages/numpy/core/include
>>  
>> -Ibuild/src.linux-x86_64-3.8/numpy/distutils/include -c -c 
>> scipy/interpolate/fitpack/curev.f -o 
>> build/temp.linux-x86_64-3.8/scipy/interpolate/fitpack/curev.o" failed with 
>> exit status 1*
>>
>>   ### CLIB COMPILER OPTIMIZATION ###
>>   Platform  :
>> Architecture: x64
>> Compiler: gcc
>>
>>   CPU baseline  :
>> Requested   : 'min'
>> Enabled : SSE SSE2 SSE3
>> Flags   : -msse -msse2 -msse3
>> Extra checks: none
>>
>>   CPU dispatch  :
>> Requested   : 'max -xop -fma4'
>> Enabled : SSSE3 SSE41 POPCNT SSE42 AVX F16C FMA3 AVX2 AVX512F 
>> AVX512CD AVX512_KNL AVX512_KNM AVX512_SKX AVX512_CLX AVX512_CNL AVX512_ICL
>> Generated   : none
>>   CCompilerOpt.cache_flush[809] : write cache to path -> 
>> /mnt/g/Maths/sage-9.5/clone/local/var/lib/sage/venv-python3.8/var/tmp/sage/build/scipy-1.7.2/src/build/temp.linux-x86_64-3.8/ccompiler_opt_cache_clib.py
>>   *error: Command "gfortran -Wall -g -ffixed-form -fno-second-underscore 
>> -g -O2 -fPIC -fPIC -O3 -funroll-loops 
>> -I/mnt/g/Maths/sage-9.5/clone/local/var/lib/sage/venv-python3.8/lib/python3.8/site-packages/numpy/core/include
>>  
>> -Ibuild/src.linux-x86_64-3.8/numpy/distutils/include -c -c 
>> scipy/interpolate/fitpack/curev.f -o 
>> build/temp.linux-x86_64-3.8/scipy/interpolate/fitpack/curev.o" failed with 
>> exit status 1*
>>   Building wheel for scipy (pyproject.toml): finished with status 'error'
>>   ERROR: Failed building wheel for scipy
>> Failed to build scipy
>> ERROR: Failed to build one or more wheels
>>
>> 
>> Error building a wheel for scipy-1.7.2
>>
>> 
>>
>> real 3m25.289s
>> user 6m14.359s
>> sys 1m47.406s
>>
>> In the re-make #12, 'sagelib-9.5' build failed with:
>> *error: [Errno 22] Invalid argument: 'sage/rings/power_series_poly.pxd'*
>>
>> Discovering Python/Cython source code
>> distributions = ['']
>> Discovered Python/Cython sources, time: 2.99 seconds.
>> running build
>> Generating auto-generated sources
>> Building interpreters for fast_callable
>> running build_cython
>> Enabling Cython debugging support
>> *error: [Errno 22] Invalid argument: 'sage/rings/power_series_poly.pxd'*
>>
>> real 0m17.411s
>> user 0m4.844s
>> sys 0m11.797s
>>
>>
>> Regards,
>>
>> phiho
>>
>>
>> On Thu, Feb 3, 2022 at 2:36 PM Matthias

Re: [sage-devel] Re: sage 9.5 build failed at package numpy-1.21.4 (on Windows Server 2019 WSL)

[Matthias Koeppe]

I think it's a bug in WSL 1. We should update our WSL install instructions 
to mention this limitation.

You could also try if switching to WSL 2 improves the situation when using 
the mounted drive.


On Wednesday, February 16, 2022 at 12:04:41 PM UTC-8 hohoa...@gmail.com 
wrote:

> Hi  Matthias,
>
> I have just finished the builds for sage 9.5 and 9.6 b01 successfully on 
> the root drive (instead of mounted drive which was OK for sage 9.4)
>
> Thank you so much for your patience. I am wondering what is the problem 
> with the mounted drive. 
> Is it a bug in WSL or  a feature in Ubuntu and/or Sage I am concerned 
> about the limited disk space on the root drive
>
> Again, thank you for your help and patience.
>
> Regards,
>
> phiho
>
>
> On Tuesday, February 15, 2022 at 11:46:41 AM UTC-5 Matthias Koeppe wrote:
>
>> I would suggest to try whether the "Invalid argument" syscall errors go 
>> away if you clone the Sage source tree in the Linux file system, for 
>> example, in "/sage", instead of a location mounted from the Windows file 
>> system (/mnt/g/Maths/sage-9.5/clone/).
>>
>>
>>
>>
>> On Tuesday, February 15, 2022 at 12:14:30 AM UTC-8 hohoa...@gmail.com 
>> wrote:
>>
>>> Hi,
>>>
>>> Thank you so much for your advice.
>>>
>>> I just started afresh with a new clone from github and following the 
>>> instructions from https://sagemanifolds.obspm.fr/install_ubuntu.html
>>>
>>> After running './configure', conda was deactivated (twice):
>>>
>>> $ which conda
>>> /home/hph/miniconda3/bin/conda
>>>
>>> $ conda deactivate
>>> $ conda deactivate
>>>
>>> Then:
>>>
>>> $ make ccache
>>> $ MAKE="make -j8" make
>>>
>>> after 10 times of -re-make (with MAKE="make -j8"):
>>>
>>> $ ls -l *.log | wc -l
>>> 152
>>>
>>> $ ls -l *.log.error | wc -l
>>> 12
>>>
>>> All the errors from the earlier make's seemed to be fixed eventually in 
>>> the later re-make, all except 'scipy-1.7.2' and 'sagelib-9.5'
>>>
>>> Please find attached 'config.log.7z' and 'Error building a wheel for 
>>> scipy-1.7.2 - scipy-1.7.2.log.error.7z' (from re-make #5 to #10) and 
>>> 'sagelib-9.5.log.error.7z'
>>>
>>> The re-make #10, scipy-1.7.2 failed with:
>>>
>>> *error: Command "gfortran -Wall -g -ffixed-form -fno-second-underscore 
>>> -g -O2 -fPIC -fPIC -O3 -funroll-loops 
>>> -I/mnt/g/Maths/sage-9.5/clone/local/var/lib/sage/venv-python3.8/lib/python3.8/site-packages/numpy/core/include
>>>  
>>> -Ibuild/src.linux-x86_64-3.8/numpy/distutils/include -c -c 
>>> scipy/interpolate/fitpack/curev.f -o 
>>> build/temp.linux-x86_64-3.8/scipy/interpolate/fitpack/curev.o" failed with 
>>> exit status 1*
>>>
>>>   ### CLIB COMPILER OPTIMIZATION ###
>>>   Platform  :
>>> Architecture: x64
>>> Compiler: gcc
>>>
>>>   CPU baseline  :
>>> Requested   : 'min'
>>> Enabled : SSE SSE2 SSE3
>>> Flags   : -msse -msse2 -msse3
>>> Extra checks: none
>>>
>>>   CPU dispatch  :
>>> Requested   : 'max -xop -fma4'
>>> Enabled : SSSE3 SSE41 POPCNT SSE42 AVX F16C FMA3 AVX2 AVX512F 
>>> AVX512CD AVX512_KNL AVX512_KNM AVX512_SKX AVX512_CLX AVX512_CNL AVX512_ICL
>>> Generated   : none
>>>   CCompilerOpt.cache_flush[809] : write cache to path -> 
>>> /mnt/g/Maths/sage-9.5/clone/local/var/lib/sage/venv-python3.8/var/tmp/sage/build/scipy-1.7.2/src/build/temp.linux-x86_64-3.8/ccompiler_opt_cache_clib.py
>>>   *error: Command "gfortran -Wall -g -ffixed-form 
>>> -fno-second-underscore -g -O2 -fPIC -fPIC -O3 -funroll-loops 
>>> -I/mnt/g/Maths/sage-9.5/clone/local/var/lib/sage/venv-python3.8/lib/python3.8/site-packages/numpy/core/include
>>>  
>>> -Ibuild/src.linux-x86_64-3.8/numpy/distutils/include -c -c 
>>> scipy/interpolate/fitpack/curev.f -o 
>>> build/temp.linux-x86_64-3.8/scipy/interpolate/fitpack/curev.o" failed with 
>>> exit status 1*
>>>   Building wheel for scipy (pyproject.toml): finished with status 'error'
>>>   ERROR: Failed building wheel for scipy
>>> Failed to build scipy
>>> ERROR: Failed to build one or more wheels
>>>
>>>