[sage-devel] Re: Using Sage on Windows

2024-10-16 Thread Kwankyu Lee
On Thursday, October 17, 2024 at 3:00:18 PM UTC+9 Kwankyu Lee wrote The wsl image tar file is of size about 6GB. It would be nice if we have a public file server to accommodate the tar file. The gzipped file is just 1.8GB. I may use release assets for some time. -- You received this mess

[sage-devel] Re: Using Sage on Windows

2024-10-16 Thread Kwankyu Lee
Another alternative would be to import the docker image as a WSL distribution. From a user perspective, this would be simply setting up WSL, downloading the docker image as a tar file and then run wsl --import SageMath . The tar file could be automatically generated from the docker image upon

[sage-devel] Re: Using Sage on Windows

2024-10-16 Thread 'tobia...@gmx.de' via sage-devel
I'm very happy to see improvements to the Windows installation. I don't have the time right now to try your powershell script, but it looks like a nice walk-through for not-so-technical users. Do you want to add it to the docs? Another alternative would be to import the docker image as a WSL d

Re: [sage-devel] Re: On `Ideal.groebner_basis(algorithm='singular:stdfglm')`

2024-10-16 Thread Vincent Neiger
A minor comment : from the documentation of Singular it seems that the output Gröbner basis will be computed with respect to the monomial ordering of the base ring. So for the specific code snippet given above with the ring constructed as "Kx.=QQ[]", I would expect step 3 (the actual change of

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

2024-10-16 Thread William Stein
For a timely example of how PyPI size limits can be very real, JupyterLab's is hitting this right now: https://github.com/jupyterlab/jupyterlab/issues/16859 ERRORHTTPError: 400 Bad Request from https://upload.pypi.org/legacy/ Project size too large. Limit for project 'jupyterlab' tot

Re: [sage-devel] Re: On `Ideal.groebner_basis(algorithm='singular:stdfglm')`

2024-10-16 Thread Oscar Benjamin
On Wed, 16 Oct 2024 at 16:45, Nils Bruin wrote: > > On Wednesday 16 October 2024 at 06:43:30 UTC-7 Georgi Guninski wrote: > > sage: Kx.=QQ[] > sage: I=Ideal([x*y]) > sage: gb=I.groebner_basis(algorithm='singular:stdfglm') > > TypeError: Singular error: > ? The ideal i has to be 0-dimensional > > I

[sage-devel] Re: On `Ideal.groebner_basis(algorithm='singular:stdfglm')`

2024-10-16 Thread Nils Bruin
On Wednesday 16 October 2024 at 06:43:30 UTC-7 Georgi Guninski wrote: sage: Kx.=QQ[] sage: I=Ideal([x*y]) sage: gb=I.groebner_basis(algorithm='singular:stdfglm') TypeError: Singular error: ? The ideal i has to be 0-dimensional I believe computing the dimension of ideal requires computing gr

Re: [sage-devel] Re: Proposal: ci codecov/patch reports but not fail

2024-10-16 Thread Dima Pasechnik
On Sat, Oct 5, 2024 at 6:06 PM John H Palmieri wrote: > > > > On Saturday, October 5, 2024 at 6:38:20 AM UTC-7 Kwankyu Lee wrote: > > But I don't know how big a problem the codecov issue is ... > > > We want to regard the check failure as there is a problem with the PR that > the author sho

[sage-devel] On `Ideal.groebner_basis(algorithm='singular:stdfglm')`

2024-10-16 Thread Georgi Guninski
sage: Kx.=QQ[] sage: I=Ideal([x*y]) sage: gb=I.groebner_basis(algorithm='singular:stdfglm') TypeError: Singular error: ? The ideal i has to be 0-dimensional I believe computing the dimension of ideal requires computing groebner basis and even if this a false, computing the dimension of ideal w

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

2024-10-16 Thread Eric Gourgoulhon
Le mardi 15 octobre 2024 à 17:18:08 UTC+2, dim...@gmail.com a écrit : Sure. However,here the problem is probably related to most WSL users sticking to the default for WSL Ubuntu LTS distro, which is likely to be 22.04, carrying giac 1.7, too old for Sage. So they'd need (i.e. Sage needs) to b

[sage-devel] Re: Proposal: ci codecov/patch reports but not fail

2024-10-16 Thread Eric Gourgoulhon
Le dimanche 6 octobre 2024 à 01:07:06 UTC+2, Kwankyu Lee a écrit : It seems we have to choose between: (1) We keep the status quo: not testing every code path created in the PR results in the PR check failure. (2) we keep codecov/patch as it is, but require to add doctests for every code pat

[sage-devel] Re: Using Sage on Windows

2024-10-16 Thread Eric Gourgoulhon
Thank you very much Julian and Sebastian for these initiatives! On ask.sagemath, we see too many messages from Windows users not managing to install Sage. A recent example is https://ask.sagemath.org/question/79640/error-during-configuration-with-wsl/ We also see messages from users stuck to Sage