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

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

[sage-devel] RFC: demote giac to optional

Hi, I've separated sage.libs.giac into its own package, and would like to downgrade giac to optional at the same time the new package is added, cf. * https://github.com/sagemath/sagemath-giac * https://github.com/sagemath/sage/pull/39376 tl;dr now is the time to object. The reason for this,

Re: [sage-devel] Admin request: new sagemath-giac repository

On Thu, 2025-02-13 at 12:51 -0500, David Roe wrote: > Hi Michael, > I've created sage-giac <https://github.com/sagemath/sage-giac> and added > you as an admin. Let me know if you need anything else. Thanks for > working on this! > David Thank you... but can you pleas

[sage-devel] Admin request: new sagemath-giac repository

Hi, this is a friendly reminder that I am trying to move the repository, https://github.com/orlitzky/sagemath-giac under the sagemath umbrella, i.e. to https://github.com/sagemath/sagemath-giac so that it can be built separately in https://github.com/sagemath/sage/pull/39376 (The repo n

Re: [sage-devel] Re: Possibly insecure verification of sage source downloaded from a mirror

On 2025-02-12 10:22:14, Nils Bruin wrote: > In my opinion, this problem is commonly solved nowadays by curated software > distributions (through stores, trusted package repositories, etc.) with > keys that are predistributed with the operating system used. The integrity > control is then offload

Re: [sage-devel] Has someone verified that sage doesn't download code over unencrypted channels?

On 2025-02-10 10:43:37, Georgi Guninski wrote: > Downloading and running code over unencrypted channels like 'http://' > is dangerous from security point of view. There's a sha256 hash in each build/pkgs//checksums.ini. So long as the developer who commits checksums.ini has either (a) verified the

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

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

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

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

Re: [sage-devel] Cython extension modules in optional spkgs

On 2025-01-26 11:03:42, Marc Culler wrote: > Yes, I have a log file for coxeter3 which built fine. > > The problem turned out to be that I had to use BOTH ---enable-coxeter3 AND > -enable-sagemath_coxeter3. With the latter option, the .so file gets build > and installed as expected. > > Why?

Re: [sage-devel] Policy for closing abandoned PRs

On 2025-01-23 10:35:13, Vincent Macri wrote: > I want to clarify a couple things that might convince the people opposed > to this (and if not I have a compromise proposal). Closing a PR doesn't > mean we lose the potential contribution. Any time you make a proposal you will get responses that sk

Re: [sage-devel] Installing 32-bit Linux on an old laptop

On 2024-12-13 15:04:58, John Cremona wrote: > Using an emulator is a good idea, I will try that if installing MX fluxbox > fails. I came to the conclusion that the USB stick I had been using > yesterday for my debian attempts was faulty,I am using a new one now. > > BUT when I said that the lapto

Re: [sage-devel] Trouble using Guava in SageMath 10.3 with GAP 4.12.2

On 2024-12-07 09:37:55, ETAL wrote: > Thank you for your reply and assistance; I truly appreciate it. However, > I’m unable to get Sage 10.4, at least not through sudo or the binaries. It > took me over seven hours to install Sage 10.3 from the source code, so I’m > just trying to make it work a

Re: [sage-devel] Trouble using Guava in SageMath 10.3 with GAP 4.12.2

On 2024-12-06 01:34:46, ETAL wrote: > > Hello, > > I am experiencing an issue using the Guava package in SageMath 10.3 with > GAP 4.12.2 installed on my system. The strange part is that *Guava works > when I use the GAP console inside Sage*, but it doesn't work when I try to > load it through

Re: [sage-devel] Re: using libgap in source

On 2024-12-05 20:31:40, Jackson Walters wrote: > > It would be nice to just have these installed. This isn't something I can > do, right? I should mention that locally this is all working in my > installation, where I have installed `forms`. > You could hold a vote to make "forms" a standard pac

Re: [sage-devel] Re: using libgap in source

On 2024-12-05 15:23:35, Jackson Walters wrote: > > Ah, thank you. Any idea if loading packages via libgap.LoadPackage("forms") > is > expected to work? Yes, but only if the GAP package you're trying to load is installed. The only ones that are guaranteed to be installed are gapdoc, primgrp, sma

Re: [sage-devel] Defining MAKE='make -j4' is recommended?

On 2024-11-13 01:12:25, Kwankyu Lee wrote: > Hi, > > According to our installation guide: > > *One useful setting for this variable when building Sage is MAKE='make > -jNUM' to tell the make program to run NUM jobs in parallel when building. > Note that some Sage packages may not support this v

Re: [sage-devel] Re: Adding functionality that depends on upgrading a standard package.

On 2024-11-01 04:32:35, Nils Bruin wrote: > There is obviously the "package version", but as I now see, the "equivalent > system packages" don't seem to encode an explicit version restriction at > all. So I guess Michael's comment on spkg-configure.m4 is probably > appropriate. I guess explicit

Re: [sage-devel] Adding functionality that depends on upgrading a standard package.

On 2024-10-31 03:55:40, mmarco wrote: > I recently released a new version of libbraiding that exposes new > functionality, in order to use those new functions from Sage (see #38887). > > However, the CI tests fail because they use the old version (taken from the > system, instead of installing

Re: [sage-devel] A new logo?

On Sun, 2024-10-20 at 02:21 -0700, Kwankyu Lee wrote: > > What do you think? I somewhat agree on both points, * The icosahedron strikes me as an instance of "hey give me the name of a cool math shape" that has nothing to do with sage itself * The font can be ugly, and if you don't know

Re: [sage-devel] Error during compilation (make) on WSL

On 2024-10-13 01:18:03, Mohamed Takouri wrote: > and during the compilation this: > make[4]: *** [Makefile:3425: giac-SAGE_LOCAL-no-deps] Error 1 make[3]: *** [ > Makefile:3425: /home/momo/sage/sage-10.4/local/var/lib/sage/installed/giac- > 1.9.0.15p0] Error 2 make[2]: *** [Makefile:3043: all-start

Re: [sage-devel] Re: [debian-science] Modularized sagemath packages: proof of concept

e GPLv3 > license. (Networkx used to be GPL licensed and they somehow managed to > relicense as BSD.) Michael Orlitzky dismissed my comments about > licensing in this thread, and I really wish he were correct. > I'm not being dismissive, I'm just trying to understand what the p

Re: [sage-devel] Re: [debian-science] Modularized sagemath packages: proof of concept

On Mon, 2024-10-07 at 07:55 -0700, William Stein wrote: > Hi, > > There are a number of big chunks of functionality in Sage, like interval > arithmetic (I was just going to say this and Marc beat me to it), and the > sage preparser, which could be valuable as separate packages that Sage uses. > >

Re: [sage-devel] ERROR [transfer|run:135]: [Errno 404] Not Found when downloading cython-3.0.11.tar.gz

On Thu, 2024-10-03 at 06:13 -0700, Sébastien Labbé wrote: > After a long period using an old version of Sage, I tried to update my > version of Sage yesterday to the latest development version, but the `make` > gets stuck while trying to download cython and maxima. See excerpt of log > below. I

Re: [sage-devel] view command

On 2024-09-27 23:45:58, Anne Schilling wrote: > Dear All, > > I see that there were some problems recently with the view command which > seem to have been fixed. However, compared to older versions of SageMath, > there still seems to be some odd behaviors. For example, the commands... If you ar

Re: [sage-devel] Re: Package upgrade PRs waiting for review

On 2024-09-25 11:55:36, Matthias Koeppe wrote: > On Monday, September 23, 2024 at 5:34:26 AM UTC-7 Michael Orlitzky wrote: > > On Sun, 2024-09-22 at 20:05 -0700, 'tobia...@gmx.de' via sage-devel > wrote: > > Matthias claims these > > are needed f

Re: [sage-devel] Re: Package upgrade PRs waiting for review

On Sun, 2024-09-22 at 20:05 -0700, 'tobia...@gmx.de' via sage-devel wrote: > Michael, to make things short: The discussion is around these changes to > the `pyproject.toml` file > https://github.com/sagemath/sage/pu

Re: [sage-devel] Re: Package upgrade PRs waiting for review

On Wed, 2024-09-18 at 16:23 -0700, Matthias Koeppe wrote: > > I would appreciate feedback from the developers working on this feature > (Dima?, Michael?) regarding how to specify these constraints now that > sage-lib defines its own constraints in pyproject.toml. > > Th

Re: [sage-devel] Python security: PyPI hijack exposes 22K+ packages to takeover attacks

On 2024-09-09 12:43:12, Georgi Guninski wrote: > > The DevOps and security firm estimates there are around 22,000 > packages in PyPI vulnerable to a revive hijack attack, and the > researchers noted they've already spotted the technique being used in > the wild to infect the pingdomv3 package. Sol

Re: [sage-devel] Automatic beta release

On Fri, 2024-08-30 at 20:26 -0700, Kwankyu Lee wrote: > > What do you think? Why not do what everyone else does, and let developers merge PRs into the "develop" branch when they're approved? Waiting only causes merge conflicts. The release manager could still cherry-pick commits for betas, relea

Re: [sage-devel] Proposal: Demote jupyter-jsmol and tachyon to optional

Playwright (via Chromium) would add another non-portable component to sage, which incidentally downloads several hundred megabytes of untrusted executable code from god-knows-where. As a distro package, tachyon is mildly annoying, but all that it really needs is a sane build system. The existing o

Re: [sage-devel] Proposal: Policy for standard packages from binary wheels

On Wed, 2024-08-07 at 06:41 +0700, Bagas Sanjaya wrote: > > In Windows, that's quite common for people to have antivirus installed. > But for people on Linux, they usually don't install one. > On Linux, people aren't usually dumb enough to download exes from strangers. Yet here we are. -- You

Re: [sage-devel] Sage-10.4 fails to build

On Fri, 2024-08-02 at 07:09 -0700, Niranjana K M wrote: > At first I had flint-3.1.0 from Gentoo portage. Got same errors and build > failed. The I uninstalled flint and its dependents from Gentoo and let the > Sage choose its flint spkg. Again it also failed with same errors. > These errors,

Re: [sage-devel] Sage-10.4 fails to build

On 2024-08-02 15:19:03, Niranjana K M wrote: > Dear Sage developers, > Sage-10.4 fails to build on my computer running with Gentoo Linux. > It uses gcc-13.3.1 and python-3.12.3. > Sagemath is the master branch from git. > It fails to build sagelib-10.4. If i search for errors in log i could fin

Re: [sage-devel] eclib version checking

On Wed, 2024-06-26 at 15:26 +0100, John Cremona wrote: > In build/pkgs/eclib/spkg-configure.m4 tere is code to check whether an > already installed version of eclib is new enough. It use to check that the > version agreed exactly, but now it uses [ge] ("greater or equal") to do > this. > Did you

Re: [sage-devel] Re: Current status of possibility of integrating libraries written in Rust into Sage

On Mon, 2024-06-03 at 12:54 -0700, Matthias Koeppe wrote: > > Could you share details regarding this? I'm not sure who "we" is in what > you write, but in the last Jupyter PR that I prepared, I had to use some > older versions of some packages to avoid pulling in the Rust dependency at > this p

Re: [sage-devel] Re: Current status of possibility of integrating libraries written in Rust into Sage

On Sat, 2024-06-01 at 10:02 -0700, Matthias Koeppe wrote: > Unlikely that we would add a package to the Sage distribution that builds a > Rust library from source. > > Not so long ago we added support for installing Python packages from > platform-independent wheels. We did this to sidestep the

Re: [sage-devel] Unreasonably slow piecewise function

On Thu, 2024-05-02 at 02:13 -0700, Kwankyu Lee wrote: > Moreover, this case seems to spur the need to introduce timing tests to > watch out regressions in code performance without a failure. > Shameless plug: https://github.com/sagemath/sage/pull/36226 I see these regressions (old hardware)

Re: [sage-devel] Re: Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

On 2024-04-20 15:33:51, Matthias Koeppe wrote: > Michael, I think you may be using too much jargon to get your point across > to the general readership of this list. > > Let's maybe use this opportunity to make this as concrete as possible and > explain it in the most

Re: [sage-devel] Re: Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

On Sat, 2024-04-20 at 15:01 -0700, kcrisman wrote: > > Can someone who is not Dima or Matthias explain to us how it is possible > that they both are claiming to represent the normal Python way of doing > things? There have been numerous statements by both of them about this, > which makes it s

Re: [sage-devel] On backdooring open source projects

On Sat, 2024-04-20 at 12:53 -0700, Emmanuel Charpentier wrote: > > Do we have the manpower necessary to such development ? . Linux distributions (or e.g. Conda) already do it for us. What we don't have is the manpower to do what we currently do, but *correctly*. The sage distribution sucks. Lots

Re: [sage-devel] Re: Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

On Sat, 2024-04-20 at 10:07 +0100, Dima Pasechnik wrote: > > Apart from Lisp, there is GAP (with the corresponding effort stalled). > > That's what is much more urgent than attempting to slice up the maths > functionality of sagelib. > Also the ancient copy of ginac/pynac we bundle. -- You r

Re: [sage-devel] Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

On Sat, 2024-04-20 at 02:22 -0700, Volker Braun wrote: > Yes in a perfect world, but then you don't get a gold star for satisfying > some purity test. We should just do the minimal amount of work to get us > where we want to be. Lets focus on the direction to go and not too much on > the process

Re: [sage-devel] Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

On Fri, 2024-04-19 at 09:46 -0700, Matthias Koeppe wrote: > > Michael, note that in my message I asked for a vote on that dependency > https://github.com/sagemath/sage/pull/36676. > Even if 36676 gets approval, 36964 must be reverted. It was not meaningfully voted upon. -- You r

Re: [sage-devel] On backdooring open source projects

On 2024-04-18 16:04:43, Lorenz Panny wrote: > > > > It's also 214 software packages which might, for all we know, at any > > time be hijacked by The Bad Guys to run arbitrarily malicious code on > > every Sage user's machine. > > > > This is terrifying. 276 now -- You received this message bec

Re: [sage-devel] Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

On 2024-04-18 14:18:37, Matthias Koeppe wrote: > Dear all: > > As an alternative to the proposal to back out the > PR https://github.com/sagemath/sage/pull/36964 whose *disputed dependency > PR https://github.com/sagemath/sage/pull/36676 which had not reached the > required 2:1 supermajority *o

Re: [sage-devel] VOTE: Revert merged PR with unreviewed dependencies

On Thu, 2024-04-18 at 11:54 -0400, David Roe wrote: > I am therefore asking you to vote (+1 means merge #37796 > in order to revert #36964 > ). +1 -- You received this message because you are subscribed to

Re: [sage-devel] Re: Proposal (redo): Make python_build (and its dependency pyproject_hooks) a standard package

On 2024-04-15 04:20:59, kcrisman wrote: > > The real question is about *users* in this case, not developers. The solution for users is pretty simple. You should be able to install a sage that works and will remain working with one command using homebrew, conda, guix, etc. The reason you can't is b

Re: [sage-devel] Re: xz/liblzma has been compromised

On 2024-03-30 07:08:45, Marc Culler wrote: > > Potentially, any tarfile we host may contain an exploit. > > Potentially, any file may contain an exploit. > > This hack specifically targeted ssh. When used by ssh to verify keys, the > hacked liblzma would validate certain invalid keys, allowing

Re: [sage-devel] No MathJax display in Sage 10.3.beta notebooks when offline

On Thu, 2024-02-15 at 13:13 -0800, Nils Bruin wrote: > According to the jupyter notebook documentation: > > https://jupyterbook.org/en/stable/content/math.html > > it should be possible to switch jupyter from using mathjax 2 to mathjax 3 > by some configuration option (no clue where those config

Re: [sage-devel] One year of Sage development on GitHub

On Thu, 2024-02-08 at 11:30 +, Dima Pasechnik wrote: > > We should not try to compete, in effect, with Conda etc, yet we do. This is > the primary reason for slowness. > My personal stats for the year 2023-02-08 through 2024-02-08: Commits: 423 Reviews: 38 Zero of those have anything t

Re: [sage-devel] Error compiling sagelib-10.2 with --enable-system-site-packages

On Sat, 2024-01-13 at 14:54 +0530, Niranjana K M wrote: > > I thought the installation would replace the previous builds when new > system packages are available. It is preferring old local spkg installs, if > already present, than new versions in system. But if it is spkg only it is > going for u

Re: [sage-devel] Error compiling sagelib-10.2 with --enable-system-site-packages

On Fri, 2024-01-12 at 09:25 -0800, Niranjana K M wrote: > Should I have had started by cleaning the previous builds? It may be still > using old Cython spkg, built when it was sage 10.0 release. Because in venv > site-packages, it still says > sage/venv/lib64/python3.11/site-packages/Cython-0.2

Re: [sage-devel] Error compiling sagelib-10.2 with --enable-system-site-packages

On Fri, 2024-01-12 at 08:33 -0500, Michael Orlitzky wrote: > > One thing I noticed is that you said "master" branch. Please try the > "develop" branch instead -- that's where the actual development takes > place. Both Sage and Gentoo are fast-moving and you&

Re: [sage-devel] Error compiling sagelib-10.2 with --enable-system-site-packages

On Fri, 2024-01-12 at 18:24 +0530, Niranjana K M wrote: > It is attached in the previous mail. > Indeed, sorry, it was my first email of the day. I have to get warmed up first. One thing I noticed is that you said "master" branch. Please try the "develop" branch instead -- that's where the actua

Re: [sage-devel] Error compiling sagelib-10.2 with --enable-system-site-packages

On Thu, 2024-01-11 at 20:56 -0800, Niranjana K M wrote: > > I am running on Gentoo Linux and sagemath is from git master branch. > I am having system cython-3.0.6 built on python-3.11.7. > > Please help me to resolve it. > Can you post your config.log? -- You received this message because you

Re: [sage-devel] Disputed Pull Requests / Role Sage-Abuse and the Code of Conduct

On Wed, 2024-01-10 at 06:49 -0800, William Stein wrote: > Dear Sage Developers, > > 1. There are over 20 pull requests labeled as "disputed" [1]. To > resolve these pull requests, we will be appointing an editor with no > direct involvement in the pull request to make a judgement call on > that p

Re: [sage-devel] Unable to compile JuPiMake

On Wed, 2023-12-20 at 16:42 +0100, Salvatore Stella wrote: > > Did you build polymake with USE=libpolymake? > > I did, before I did not and sage build system refused to use my system's > polymake. > Hm, my next guess is then https://github.com/sebasguts/JuPyMake/issues/4 since I think that'

Re: [sage-devel] Unable to compile JuPiMake

On Wed, 2023-12-20 at 16:13 +0100, Salvatore Stella wrote: > > I have polymake 4.11 installed through my system package manager (gentoo) and > I am using gcc 13.2.1. The same issue happens if I try to install JuPiMake > though the sage build system, using pip through PyPi in a virtualenv, and >

[sage-devel] Removing Cygwin support

We dropped Cygwin support in September 2022, https://github.com/sagemath/sage/wiki/Sage-9.7-Release-Tour but that was mainly a documentation change reflecting the fact that Cygwin support had bit-rotted. Anyone could have fixed it at that point -- or in the meantime -- but no one has done so.

Re: [sage-devel] Pillow built without jpeg support in Sage 10.2.rc3

On Fri, 2023-11-17 at 10:49 -0800, Marc Culler wrote: > I expect to receive lots of flak for saying this, but I support making > libjpeg be a standard spkg using the source code from > https://libjpeg.sourceforge.net. I just built version jpeg-9e on Ubuntu > 18.04 and macOS 10.13. The standard

Re: [sage-devel] Pillow built without jpeg support in Sage 10.2.rc3

On Fri, 2023-11-17 at 17:26 +, Dima Pasechnik wrote: > > Why can't Features be set up by ./configure ? You'll tell me that > (some) distributions don't run ./configure, but this is beside the > point. > They have ways to know what's installed and what's not installed. > I think the problem i

Re: [sage-devel] Pillow built without jpeg support in Sage 10.2.rc3

On Fri, 2023-11-17 at 02:33 -0800, Eric Gourgoulhon wrote: > On 17 November 2023 04:35:53 GMT, Matthias Koeppe > wrote: > > Or we just let pillow use a system libjpeg if it finds one. > > This would probably be the easiest solution: I cannot imagine a system > without libjpeg... I don't know

Re: [sage-devel] Pillow built without jpeg support in Sage 10.2.rc3

On Thu, 2023-11-16 at 06:48 -0800, Eric Gourgoulhon wrote: > > If we agree to restore jpeg support in Pillow, I have prepared a branch > that does this for Sage 10.2 (simply suppressing the option "jpeg=disable"): > https://github.com/egourgoulhon/sage/tree/pillow_jpeg > and I am happy to submit

Re: [sage-devel] eclib dependencies

On 2023-11-16 09:23:15, John Cremona wrote: > > If no-one has any reason to keep things as they are I will make a PR with > the relevant changes to build/pkgs/eclib. >From a packaging standpoint, fewer dependencies is better. For example, upgrading flint would become a tiny bit easier if we didn'

Re: [sage-devel] Re: Cython errors when building p_group_cohomology

On 2023-11-16 00:51:12, Dima Pasechnik wrote: > This package produces mathematically incorrect results, as was shown > on a trac ticket a couple of years ago, and no movement then. Demote > to experimental? There's not much distinction at this point, but if we're going by the "builds on supported

Re: [sage-devel] Re: Question about make dependencies

On 2023-11-14 23:44:50, Dima Pasechnik wrote: > I have not invented the verb "to vendor" Don't worry, you are in good company: https://www.gocomics.com/calvinandhobbes/1993/01/25 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe fro

Re: [sage-devel] Re: Question about make dependencies

On Tue, 2023-11-14 at 09:42 -0800, Marc Culler wrote: > Of course I meant that I have to wait for everything that *depends on* gmp > to be recompiled. Also, this happens when there is nothing wrong with the > gmp build. The make system decides that it is out of date even though the > build was

Re: [sage-devel] Fedora sagemath package maintainer

On Sat, 2023-09-30 at 14:36 -0700, enriqu...@gmail.com wrote: > I have learnt that at this momente there is no Fedora sagemath package > maintainer. I am a Fedora user but I do not use the rpm package; more > relevant, I do not have the skills for this maintenance. > Would anyone take the task? >

Re: [sage-devel] Poll: deprecate backslash operator

On Sat, 2023-09-30 at 14:47 -0700, John H Palmieri wrote: > > This is not used much: for matrices, matroids, and a tiny bit (at least in > the Sage library) for binary trees. Should we deprecate it? Deprecate it, it's a big WTF for most people. -- You received this message because you are subs

Re: [sage-devel] Discussion and poll: should Sage Integers have a backslash operator?

On Wed, 2023-09-27 at 14:44 -0700, Nils Bruin wrote: > Searching the codebase currently only shows "_backslash_" implemented on > matroid, matrix, and binary_tree, so extinguishing it should be doable. We > should definitely not entrench its use further. > > If you want to write your denominato

Re: [sage-devel] @options() decorators in sagemath library code and Sphinx 7.1+

On 2023-09-16 14:09:04, Dima Pasechnik wrote: > > Anyhow, if this is the only problem with upgrading to Sphinx 7.1+ (or 8) > it ought to be fixed, so that we can move on on Sphinx update. > (see https://github.com/sagemath/sage/pull/35658) My vote would be to replace the weird sageism with the st

Re: [sage-devel] @options() decorators in sagemath library code and Sphinx 7.1+

On Sat, 2023-09-16 at 13:16 +0100, Dima Pasechnik wrote: > Isn't it true that the above may be simplified, removing foo=bar from > @options() and putting this in the function definition, i.e. > AFAIK it's just dictionary unpacking that happens by default. You can already create your own options l

Re: [sage-devel] pull requests recently updated

On Wed, 2023-08-23 at 01:36 -0700, 'Martin R' via sage-devel wrote: > > Is there a way to fix this? > Now's an OK time to stop adding meaningless milestones to every open ticket. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe fr

Re: [sage-devel] why sagemath creates so many file in TMPDIR and how to prevent this?

On Tue, 2023-08-15 at 08:09 -0700, 'Nasser M. Abbasi' via sage-devel wrote: > Here is the basic flow of the script: (this is not the real script but > a stripped down version) > For now at least, initializing the sage library creates one directory under /tmp where all of sage's other temporary fi

Re: [sage-devel] why sagemath creates so many file in TMPDIR and how to prevent this?

On Tue, 2023-08-15 at 03:33 -0700, 'Nasser M. Abbasi' via sage-devel wrote: > Each time I run a sagemath script, I see 10's of thousands of files created > in my TMPDIR which I have to keep manually deleting. There aren't too many parts of sage that use temporary files. What's the script doing?

Re: [sage-devel] Re: How to use maxima 5.47 with sagemath 10.1 beta?

On 2023-07-15 19:05:42, 'Nasser M. Abbasi' via sage-devel wrote: > Maxima uses SBCL lisp: > > >maxima > Maxima 5.47.0 https://maxima.sourceforge.io > using Lisp SBCL 2.3.3 > > Are there any step-by-step instructions then how to make sagemath 10.1 use > maxima 4.7? > Not really. You need the

Re: [sage-devel] Re: How to use maxima 5.47 with sagemath 10.1 beta?

On 2023-07-15 18:56:09, Nils Bruin wrote: > It must be maxima running on ECL and there must be a > maxima.fas lisp package for ecl (which isn't built in the vanilla maxima > build). That part is finally upstream in maxima-5.47. -- You received this message because you are subscribed to the Goo

Re: [sage-devel] Memory leak (quite bad)

On 2023-07-06 09:16:46, Nils Bruin wrote: > > On Wednesday, 5 July 2023 at 08:29:44 UTC-7 Edgar Costa wrote: > > > > Hi Gonzalo, > > > > I highly recommend using https://github.com/rfjakob/earlyoom instead of > > waiting for OOM to kick in. > > Wouldn't setting ulimit with -m (memory) or -v (vi

Re: [sage-devel] Question about reading Sage documentation

On 2023-06-29 20:50:11, Marc Culler wrote: > I was asking a very specific question about SageMath on Ubuntu 22.04: Are > Ubuntu 22.04 users who install the sagemath-doc package able to read those > (Sage 9.5) docs with Firefox? If you use pip, or ./configure && make && make install to /usr/local,

Re: [sage-devel] Question about reading Sage documentation

On 2023-06-29 14:46:00, Marc Culler wrote: > During our recent release of SnapPy we ran across an issue which is likely > relevant to whether Sage's documentation is viewable on newer Ubuntu > systems (such as 22.04). The issue is that these newer Ubuntu systems ship > Firefox as a snap. A sna

Re: [sage-devel] Graphics files in Sage documentation

On 2023-06-29 23:30:57, Dima Pasechnik wrote: > On Thu, Jun 29, 2023 at 3:24 AM Michael Orlitzky wrote: > > > > On 2023-06-28 23:27:22, Dima Pasechnik wrote: > > > One can always start a web server on localhost, instead of using file:/// > > > :P > > >

Re: [sage-devel] Graphics files in Sage documentation

On 2023-06-28 23:27:22, Dima Pasechnik wrote: > One can always start a web server on localhost, instead of using file:/// :P > I know you're mostly joking, but that's not as easy as it sounds. To start the local web server as a non-root user, you have to run it on an unprivileged (i.e. not the def

Re: [sage-devel] Graphics files in Sage documentation

On Wed, 2023-06-28 at 13:50 -0400, Michael Orlitzky wrote: > > * gzipped SVG doesn't work over the file:/// protocol in my firefox. > This hasn't been a big enough problem for me yet to diagnose it, > so I can't say how serious a problem it is. (I'

Re: [sage-devel] Graphics files in Sage documentation

On Wed, 2023-06-28 at 10:07 -0700, Marc Culler wrote: > > BOTTOM LINE: we get more than a 90% reduction in size simply by choosing to > use the .svg extension when saving the plot instead of the .png extension. > SVG is the right choice for most graphics, but there are some practical problems:

Re: [sage-devel] Modularization project: I. The goals

On Thu, 2023-06-22 at 14:41 -0700, William Stein wrote: > > WebAssembly is not an experimental linux distribution, and it has very > little overlap with linux distributions. The WebAssembly ecosystem is > built from the ground up, primarily on the LLVM (and Rust) toolchain, and > an ecosystem of

Re: [sage-devel] Modularization project: I. The goals

On Thu, 2023-06-22 at 13:56 -0700, William Stein wrote: > > (5) provide a WebAssembly option > > WebAssembly is typically about half the speed as native code (at best), but > it is highly cross platform and self contained. WebAssembly is difficult > mainly when you have to deal with the OS some

Re: [sage-devel] Modularization project: I. The goals

> On 2023-06-15 18:08:35, 'Travis Scrimshaw' via sage-devel wrote: > > That is simply not true right now. The # optional sage.* doctests as a > user-visible change. > These tags aren't essential to the modularization itself. They're an artifact of bad tests: * doctests are in general just a

Re: [sage-devel] Modularization project: I. The goals

On Thu, 2023-06-08 at 14:09 -0700, Matthias Koeppe wrote: > > *D. *As a consequence of B and C, it was *impossible to build or run parts > of the Sage library.* And it is *impossible to install the whole Sage > library using Python infrastructure* (pip). (Yes, I know that conda exists.) > Of i

Re: [sage-devel] ping - please cast you vote: VOTE: Follow NEP 29: Recommended Python version

On Tue, 2023-05-30 at 10:15 +0100, Dima Pasechnik wrote: > So far we only had very few votes cast. > We probably should have started with the discussion and then voted afterwards. FWIW I'm still not sure. I basically agree with Matthias's points. If (for example) supporting python-3.8 costs us v

Re: [sage-devel] Re: VOTE: Follow NEP 29: Recommended Python version

On 2023-05-28 16:20:02, Dima Pasechnik wrote: > > indeed, https://github.com/sagemath/sage/issues/29023 is the meta-ticket to > oversee this process. Needless to say this needs more effort. I'm sure it's out of date for boring reasons, but the branch from 29665 worked great: https://github.com/sa

Re: [sage-devel] Re: VOTE: Follow NEP 29: Recommended Python version

On Fri, 2023-05-26 at 18:15 +0100, Oscar Benjamin wrote: > > What is wrong with Sage just saying that an older version of an > operating system only works with an older version of Sage? Matthias alluded to this when he mentioned that we only have one release branch of sage. Our version numbers ar

Re: [sage-devel] What was/is/will be the purpose of maintaining the Sage distribution?

On Mon, 2023-05-22 at 12:50 -0700, Matthias Koeppe wrote: > > On Saturday, April 29, 2023 at 1:45:31 PM UTC-7 TB wrote: > > Should `sage -i pandoc`, at least in an interactive session, first > recommend to install it from the distro, and not default to conda? > Eventually I think the "sage" s

Re: [sage-devel] Meson Build System

On Tue, 2023-05-02 at 10:35 -0700, Volker Weißmann wrote: > Hello, > > I'm a developer that worked quite a bit with the meson build system and > looked at sagemath for a few days. I thought that redoing the build > system with meson instead of autoconf would be quite a bit of work, but > woul

Re: [sage-devel] What was/is/will be the purpose of maintaining the Sage distribution?

On Sat, 2023-04-29 at 13:10 -0700, Matthias Koeppe wrote: > > This drops platform support for 32-bit Linux (see > https://github.com/sagemath/sage/wiki/Sage-9.8-Release-Tour#availability-of-sage-98-and-installation-help) > > for these optional packages. We will need a decision if this OK. > G

Re: [sage-devel] Re: What was/is/will be the purpose of maintaining the Sage distribution?

On Fri, 2023-04-28 at 18:06 +0100, Dr. David Kirkby wrote: > > To me at least, it would be unwise not run the test suite. > > If you are choosing to use 15-20 year old hardware, you can not reasonably > to handle a large modern program like Sagemath. More modern machines than > that get thrown in

Re: [sage-devel] Re: [sage-release] Sage 10.0.rc0 released

On Thu, 2023-04-27 at 12:37 -0700, Matthias Koeppe wrote: > A problem only arises when you try to build a bleeding-edge sage on an older > stable distro -- an undertaking unsupported by most projects. > > Is it? I would say that Sage is very special in this regard because of its > extreme number

Re: [sage-devel] Re: What was/is/will be the purpose of maintaining the Sage distribution?

On Thu, 2023-04-27 at 05:49 -0700, William Stein wrote: > Hi, > > To what extent does or could Conda with a little more work solve most > of these problems? There are some notes below from me poking around, > and I'm very optimistic. This isn't the first time the idea has come up. Burcin got pr

Re: [sage-devel] Re: [sage-release] Sage 10.0.rc0 released

On Thu, 2023-04-27 at 08:38 -0700, Nils Bruin wrote: > > But another problem before was that the different packages would not > develop in lockstep. Some components might need one specific version of > prerequisites and others another. So one could run into genuine version > conflicts. In theo

Re: [sage-devel] Re: What was/is/will be the purpose of maintaining the Sage distribution?

On Thu, 2023-04-27 at 05:12 -0700, kcrisman wrote: > > As an example, how old of a Windows computer could one install the current > Sage on? ... > > In any case, it would be very helpful for people who may be actively using > Sge in less-resourced environment to chime in here. > My desktop is

Re: [sage-devel] Re: [sage-release] Sage 10.0.rc0 released

On 2023-04-26 19:59:01, Matthias Koeppe wrote: > On Wednesday, April 26, 2023 at 7:37:17 PM UTC-7 Michael Orlitzky wrote: > > Just as a data point, eliminating the spkg and only supporting system PARI > 2.15.x would have the effect to eliminate support of: > - all versions of Ub

  1   2   3   4   5   6   7   8   9   10   >