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

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 s

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

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/con

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

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.

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

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 em

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

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

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

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://

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

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 answe

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

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

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

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-devel] Re: Conda package for Sage

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

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

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://

Re: [sage-devel] pip install on MacOS

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, > > An

[sage-devel] Re: Normaliz and parallel doctest

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

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

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 tha

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

, 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: >> >

Re: [sage-devel] Sage Python 3 proposal

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 insta

[sage-devel] Re: copying MixedIntegerLinearProgram problem

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 m

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

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 dif

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

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/interfa

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

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, sa

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

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,

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

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

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

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

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

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 pi

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

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

Re: [sage-devel] Re: python3 status

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

Re: [sage-devel] Re: python3 status

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 m

Re: [sage-devel] Patching policy

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

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

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

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

+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, 20

[sage-devel] Re: Piecewise affine functions

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 intere

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

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, > > >

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

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 line

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

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:

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

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, 20

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

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

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

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 ticke

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

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 < > ... < sagema

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

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* <

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

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 distrib

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

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/s

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

-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; h

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

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

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

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 >

[sage-devel] trac.sagemath.org down

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 h

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

m > > 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 >>

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

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 pos

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

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 rec

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

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 recompi

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

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 fee

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

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

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

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 f

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

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 suppor

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

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 u

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

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 ? &g

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

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" CFLAG

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

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 rest

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

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, 1

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

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

[sage-devel] Proposal: Stop providing binary distributions

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 t

[sage-devel] GitPod

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.s

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

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 cour

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

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 distri

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

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

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

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 fo

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

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" grou

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

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 i

Re: [sage-devel] Re: 32768

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

Re: [sage-devel] Re: 32768

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 buildi

Re: [sage-devel] Re: 32768

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 s

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

agemath.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

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

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 sectio

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

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 >

[sage-devel] Patchbot/CI improvements

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

Re: [sage-devel] Patchbot/CI improvements

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: > &

[sage-devel] Re: Patchbot/CI improvements

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: >

[sage-devel] Re: Patchbot/CI improvements

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 Matth

[sage-devel] Re: Patchbot/CI improvements

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

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

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 v

[sage-devel] Re: Parallel docbuild

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 para

[sage-devel] Re: Parallel docbuild

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 a

[sage-devel] Re: Parallel docbuild

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: > &

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

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 plat

[sage-devel] Sage and the Pyjion JIT compiler

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

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

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:

[sage-devel] Re: docbuild aborting on warnings

+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

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

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. */ | ^

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

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, 2

[sage-devel] Re: minimal requirements

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,

[sage-devel] Re: minimal requirements

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. > &

[sage-devel] Re: minimal requirements

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 infor

[sage-devel] Patchbot on GitHub Actions

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-

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

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. > > O

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

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 us

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

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

[sage-devel] Re: New trac status badges

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, t

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

ght 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://

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

> > 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 > distrib

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

(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 &q

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

n 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: > >>

  1   2   3   4   5   6   7   8   9   10   >