[sage-devel] Re: sensational bug!

Indeed, interesting. but *not confirmed* on my machine (Intel(R) Core(TM) i5-4690 on Linux ubuntu 22.04.4 LTS) Frédéric Le mercredi 6 mars 2024 à 10:47:36 UTC+1, Martin R a écrit : > On > https://github.com/sagemath/sage/actions/runs/8168335359/job/22330264302?pr=37545 > > I see > > sage -t

[sage-devel] doctest logs are unusable

Hello, since the latest develop, our doctest logs in gihtub are problematic. They are filled with thousands of lines like those below, that prevent doing anything useful. Frederic 20 optional tags:

[sage-devel] Re: Our github checks...

now it's a step related to codecov that takes more than 1h50 minutes, see https://github.com/sagemath/sage/actions/runs/6523545241/job/17714302017?pr=36463 Le mardi 10 octobre 2023 à 16:29:01 UTC+2, Kwankyu Lee a écrit : > Hi, > > I am sorry to say this, but our github checks seem to be a mess.

[sage-devel] opinions requested on x + y behaviour for polynomials

Dear all, currently, if x and y are in two different polynomial rings, one cannot add them. I propose in https://github.com/sagemath/sage/pull/36138 a sketch of changes that would build a common polynomial ring by taking the union of variables. This does not break too many things. Instead

[sage-devel] Re: images lacking on docker hub

od. Maybe it would simplify things if we only > continued stable releases on DockerHub. > > Sebastian > Frédéric Chapoton schrieb am Samstag, 15. Juli 2023 um 18:48:08 UTC+2: > >> Hello, >> >> Anybody with some docker expertise who would like to help us having >>

[sage-devel] Re: images lacking on docker hub

fair amount of work and, again >> since I am not using the images, I don't feel very motivated to champion >> that process.) >> >> julian >> >> On Thursday, May 11, 2023 at 3:27:20 PM UTC+3 Frédéric Chapoton wrote: >> >>> asking again : who has the righ

Re: [sage-devel] Re: images lacking on docker hub

elease of >> SageMath, something in the build process breaks typically. We could migrate >> this to GitHub workflows but it's also a fair amount of work and, again >> since I am not using the images, I don't feel very motivated to champion >> that process.) >> >>

[sage-devel] Re: images lacking on docker hub

asking again : who has the rights for the docker user *sagemathadmins* ? Frédéric Le dimanche 23 avril 2023 à 10:33:42 UTC+2, Frédéric Chapoton a écrit : > There are some instructions for that at the top of our docker/Dockerfile. > But I guess there is also a matter of rights, no

[sage-devel] web site from cocalc but in our domain

Hello, I have recently found: https://sage.sagemath.org/ which seems to be advertisment for cocalc. Is this something we allowed ? Frédéric -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails

[sage-devel] Re: images lacking on docker hub

There are some instructions for that at the top of our docker/Dockerfile. But I guess there is also a matter of rights, no ? Who is allowed to do that ? Maybe Julian ? Le mercredi 5 avril 2023 à 10:18:27 UTC+2, Frédéric Chapoton a écrit : > Hello, > > it seems that no recent image is

[sage-devel] images lacking on docker hub

Hello, it seems that no recent image is available on docker hub: https://hub.docker.com/search?q=sagemath%2Fsage In particular, 9.8 is not there. Is there a way to manually update that, if there is no automatic mechanism to do the job ? Frédéric -- You received this message because you are

[sage-devel] patchbots off

Hello, following the recent major changes to our workflow, I will soon turn off the "patchbot server" machine. This will have the side effect of breaking the round "patchbot report" icons in the frozen trac website. To people running "patchbot clients", please stop your machines. You may want

[sage-devel] Re: Different results for numerical and symbolic integration

note also that this works fine when the exponent is a variable ( I cannot post directly to sourceforge, sorry) (%i2) expand (diff (integrate (x*log(x)^n/(1 + x^2), x), x)); n x log (x) (%o2)

[sage-devel] Re: Different results for numerical and symbolic integration

) --- 2 13 x + 13 Le dimanche 30 octobre 2022 à 23:49:31 UTC+1, pvit...@gmail.com a écrit : > Ok, thanks a lot. I already reported the bug. > > El domingo, 30 de octubre de 2022 a las 10:27:23 UTC+1, Frédéric Chapoton > escribió: >

[sage-devel] Re: Different results for numerical and symbolic integration

please post here the link to your report Le dimanche 30 octobre 2022 à 23:49:31 UTC+1, pvit...@gmail.com a écrit : > Ok, thanks a lot. I already reported the bug. > > El domingo, 30 de octubre de 2022 a las 10:27:23 UTC+1, Frédéric Chapoton > escribió: > >> The factor-2 pr

[sage-devel] Re: Different results for numerical and symbolic integration

x*log(x)^4/(x^2 + 1) > > I will try to report the bug to maxima. But, as far I can see > https://sourceforge.net/p/maxima/bugs/ is very quiet, with few answers to > the reports. > > El lunes, 24 de octubre de 2022 a las 21:33:41 UTC+2, Frédéric Chapoton > escr

[sage-devel] Re: Different results for numerical and symbolic integration

where we can see that there is a factor 2 between the wrong symbolic value and the correct numeric value This should be filed as a bug in maxima. Le lundi 24 octobre 2022 à 21:24:30 UTC+2, Frédéric Chapoton a écrit : > and one more step : > > sage: integrate(x*log(x)^4/(x^2 + 1),

[sage-devel] Re: Different results for numerical and symbolic integration

) (-23.90778787384685, 1.267767046897461e-08, 483, 0) Le lundi 24 octobre 2022 à 21:19:46 UTC+2, Frédéric Chapoton a écrit : > more study of the bug (coming from maxima) > > sage: C=x^2*(log(x))^4/((x+1)*(1+x^2)) > sage: aa,bb=C.partial_fraction_decomposition() > sage: integral(aa,x,0,1

[sage-devel] Re: Different results for numerical and symbolic integration

more study of the bug (coming from maxima) sage: C=x^2*(log(x))^4/((x+1)*(1+x^2)) sage: aa,bb=C.partial_fraction_decomposition() sage: integral(aa,x,0,1) -5/128*pi^5 + 45/64*zeta(5) sage: integral(bb,x,0,1) 45/4*zeta(5) sage: _+__ -5/128*pi^5 + 765/64*zeta(5) sage: _.n() 0.440633136273039 sage:

[sage-devel] BROADCAST : Trac maintenance

Dear Sage developers, in order to try to fix better the recent upgrade, the *trac web server will be turned off this saturday 10/09/2022*, from 7.00 (Paris time) to 23:00 (Paris time ; https://time.is/Paris). PLEASE take again a short break and resume using trac next week! Sorry for the

[sage-devel] Ignoring invalid distribution -agemath-standard

When compiling, I see many of these strange warnings. Note the "agemath" Any idea about what is happening ? Here is one in extenso : [sagelib-9.7.rc1] WARNING: Ignoring invalid distribution -agemath-standard (/home/.../sage/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages)

[sage-devel] Re: BROADCAST MESSAGE

022 at 3:30:55 AM UTC+9 Eric Gourgoulhon wrote: >> >>> Thank you so much Frédéric at al. for all the work in setting up the new >>> Trac! >>> >>> Eric. >>> >>> >>> Le dimanche 4 septembre 2022 à 09:32:42 UTC+2, Frédéric Chapoton a

[sage-devel] Re: Unable to find SSH Key Tab in Preferences

Sorry, but this is still broken. We are aware of this issue. The ssh keys tab in the preferences is currently disactivated. Frédéric Le mardi 6 septembre 2022 à 04:12:06 UTC+2, yueqi@gmail.com a écrit : > Hi All, > > I could not push the changes to sage since the permission denied. I tried

[sage-devel] Re: BROADCAST MESSAGE

Trac 1.2 comes with various changes, including display of full names and internationalisation. You may want to look in your user preferences to customize some of these if you prefer. Le dimanche 4 septembre 2022 à 01:32:35 UTC+2, Kwankyu Lee a écrit : > Trac is now in version 1.2. Thanks! --

[sage-devel] BROADCAST MESSAGE

Dear Sage developers, in order to try to fix the recent upgrade, the *trac web server will be turned off this saturday 03/09/2022*, from 7.00 (Paris time) to 23:00 (Paris time ; https://time.is/Paris). PLEASE take again a short break and resume using trac next week! Sorry for the inconvience,

[sage-devel] Re: Trac no longer seems to push to sagetrac-mirror

the database is perfectly safe. We have daily backups (snapshots of the full machine by google) Le vendredi 2 septembre 2022 à 08:37:55 UTC+2, Kwankyu Lee a écrit : > Trac is currently running in *survival mode*. > > > Is the database safe? Was it backed up? Or can it be cloned to other >

[sage-devel] Re: Trac no longer seems to push to sagetrac-mirror

You are very welcome to help. Something has been broken in trac, and nobody understands how to fix that correctly. Trac is currently running in *survival mode*. I do intend to try fix that, but it's not my job and few people proposed to help, but many complained. I do think that this is

[sage-devel] Re: Issue with the Dependencies field in Trac pages

Trac is currently in "survival mode". There are several broken things. And it seems that it is running on some kind of obsolete or duplicate configuration. Nobody has any clear idea of the exact situation. Le jeudi 1 septembre 2022 à 10:28:16 UTC+2, Eric Gourgoulhon a écrit : > Hi, > > Maybe

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

just be patient and spend your day doing something else, please Le mercredi 31 août 2022 à 11:25:04 UTC+2, emanuel.c...@gmail.com a écrit : > > > Le mercredi 31 août 2022 à 09:46:59 UTC+2, dim...@gmail.com a écrit : > >> roll back. >> > > Do you mean > - you plan to roll back, or > -

[sage-devel] BROADCAST MESSAGE : trac down this sunday

Dear Sage developers, in order to update the underlying machine, the *trac web server will be turned off this sunday*, from 7.00 (Paris time) to 23:00 (Paris time ; https://time.is/Paris). PLEASE take a short break and resume using trac next week! Hopefully, the update will go smoothly and

[sage-devel] Re: new py file not recognized in doctests

Please forget about that. It works now. It was entirely my fault, sorry for the noise. Le lundi 20 juin 2022 à 12:17:22 UTC+2, Frédéric Chapoton a écrit : > Hello, > using the fresh develop 9.7.b3 ; > I am trying to add a new python file. > Doing "sage -b" and "make

[sage-devel] new py file not recognized in doctests

Hello, using the fresh develop 9.7.b3 ; I am trying to add a new python file. Doing "sage -b" and "make build" works BUT when using "sage -t my_new_file.py", the doctests fails because the imports from this file fails. The same imports work ifine nside the console. What is the problem ? Something

[sage-devel] can no longer push to trac from ubuntu 22.04

Hello, Since I recently upgraded my ubuntu to 22.04, I cannot push from and pull to g...@trac.sagemath.org: Permission denied (publickey). I suspect some incompatibility between my brand-new local ssh installation and the one on the trac server. Maybe the trac server should be updated to use

[sage-devel] Re: patchbot owners, please update to 3.0.3

velopment release comes out? > Or is there a way to refer to them that persists a bit longer? > > Thanks for maintaining sage-patchbot! --Samuel > > 2022-01-21 20:55:36 UTC, Frédéric Chapoton: > > > > lrslib doctests in game_theory/parser.py are fixed in #33101 (positive > rev

[sage-devel] Re: patchbot owners, please update to 3.0.3

lrslib doctests in game_theory/parser.py are fixed in #33101 (positive review) Le vendredi 21 janvier 2022 à 13:40:17 UTC+1, Samuel Lelievre a écrit : > Hi Frédéric, > > I have upgraded to sage-patchbot 3.0.4 on "pascaline". > > On Sage 9.5.rc2, "ticket 0" failed with >

[sage-devel] Re: patchbot owners, please update to 3.0.3

and to fix the remaining doc-cleaning issue, please upgrade again to the master branch of github (aka tag 3.0.4) (I would appreciate answers, rather than full silence) Frédéric Le vendredi 14 janvier 2022 à 21:25:11 UTC+1, Frédéric Chapoton a écrit : > also patchbots have persistent probl

[sage-devel] Re: patchbot owners, please update to 3.0.3

also patchbots have persistent problems with building docs. Can the people that changed something to doc-building please repair the patchbot accordingly ? pull request on github, please https://patchbot.sagemath.org/ticket/33157/ Le vendredi 14 janvier 2022 à 17:40:27 UTC+1, Frédéric Chapoton

[sage-devel] patchbot owners, please update to 3.0.3

Hello, github has removed the git: protocol. So patchbots need to be updated. please update your patchbot to the latest available tag Frédéric -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving

[sage-devel] Re: Building Sage 9.4 (source) on Ubuntu 21.10 failed

see https://trac.sagemath.org/ticket/32576 Le vendredi 17 décembre 2021 à 04:08:36 UTC+1, Kiran Kedlaya a écrit : > I have the same difficulty with 9.5beta8. I believe the issue with > cysignals is the same one reported with other distributions, like Fedora: >

[sage-devel] all patchbots fail on integer.pyx

Hello, it seems that all patchbots currently break on a doctest in integral.pyx, see below. The cause is not identified so far. Could be random-seed usage, changes in gmp, or anything else. Any idea ? Frédéric File "src/sage/rings/integer.pyx", line 6434, in

[sage-devel] Re: workers for docker images on gitlab

Same problem still stands. We will not have docker images for 9.4. Can somebody care ? Frederic Le jeudi 1 avril 2021 à 09:54:22 UTC+2, Frédéric Chapoton a écrit : > Hello, > > it would be good to make sure that sage 9.3 will have a correct docker > image. > But since r

[sage-devel] Re: trying to run a patchbot

convex63 is unhappy because of 'No space left on device' see for example report on https://patchbot.sagemath.org/ticket/30862/ Le samedi 14 août 2021 à 13:48:58 UTC+2, axio...@yahoo.de a écrit : > > I was trying to set up a patchbot, but failed. It always ends with the > message > > 0:

[sage-devel] Re: trying to run a patchbot

What config file do you pass to the patchbot ? try to pass nothing in 'tested_files'. Le samedi 14 août 2021 à 13:48:58 UTC+2, axio...@yahoo.de a écrit : > > I was trying to set up a patchbot, but failed. It always ends with the > message > > 0: Pending > ok (report successfully posted) >

Re: [sage-devel] spoken languages and banner translations

Kwankyu, may I presume that you are korean or speak korean ? If so, would you please tell if the korean banner is translated correctly, or suggest a better translation ? Frédéric Le mercredi 7 juillet 2021 à 03:58:36 UTC+2, Kwankyu Lee a écrit : > On Monday, July 5, 2021 at 9:52:21 PM UTC+9

[sage-devel] Re: possible bug: numerical approx exp, pi, sinh, cosh...

Well, it works with the real ball field or with more precision : R = RBF a = exp(-12*pi) R(a),a.n(100) ([4.2411511830161e-17 +/- 2.87e-31], 4.2411511830160775440174644060e-17) Another place to ask questions is https://ask.sagemath.org/ Le lundi 5 juillet 2021 à 08:04:44 UTC+2, Brian Lawrence a

Re: [sage-devel] spoken languages and banner translations

zoek-organisatie/broncode-vrijgegeven > (note uses of "open source", "ICT" (meant as an english acronym, although > a translation would have the same letters). Indeed, a good effort in using > the word "broncode" in various places. > > On Friday, 2 July 2021

Re: [sage-devel] spoken languages and banner translations

in Dutch. (maybe you can > write "opensource" or "open bronnen") > > > > On Fri, 2 Jul 2021, 10:18 Frédéric Chapoton, wrote: > >> Hello, >> >> if you speak interesting languages, could you please have a look at >> >> https://wiki.sagemath.

[sage-devel] spoken languages and banner translations

Hello, if you speak interesting languages, could you please have a look at https://wiki.sagemath.org/CorporateIdentity and either check the text of existing banners or suggest new translations ? The reference for the translations is the english text : "open source mathematics". thanks,

Re: [sage-devel] .configure stalls

This *very ugly hack* of pip-installing numpy allowed me to compile sage and get a seemingly working sage. I agree that this is in no way a satisfactory solution. Le lundi 21 juin 2021 à 18:26:26 UTC+2, dim...@gmail.com a écrit : > On Mon, Jun 21, 2021 at 4:45 PM Frédéric Chapoton >

Re: [sage-devel] .configure stalls

pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm pti tpr_shadow vnmi flexpriority dtherm ida bugs : cpu_meltdown

Re: [sage-devel] .configure stalls

Thanks a lot, Dima. Indeed. I removed the /usr/local/bin/gp and configure went smoothly. I think I have a similar problem with pip, but not sage-related. Frederic Le dimanche 20 juin 2021 à 23:18:15 UTC+2, dim...@gmail.com a écrit : > On Sun, Jun 20, 2021 at 8:58 PM Frédéric Chapo

[sage-devel] .configure stalls

Hello, after pulling 9.4.beta2, I got some problems with numpy compilation. I thought I solved them in some ad-hoc way but then I started to get problems with pip and tornado. In despair, I typed "make disclean" which I try hard to avoid usually, as my machine is very slow. But now, even

[sage-devel] workers for docker images on gitlab

Hello, it would be good to make sure that sage 9.3 will have a correct docker image. But since recently (9.3.b9), the gitlab setting seems no longer to work. https://gitlab.com/sagemath/sage/-/pipelines Maybe missing workers ? Can somebody do domething please ? Frédéric PS. Please patchbot

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!]

Erik, did you stop the Orsay runners for gitlab ? It seems that the docker build there for 9.3.b9 is stuck by lack of runners. https://gitlab.com/sagemath/sage/-/pipelines Frédéric Le jeudi 11 mars 2021 à 13:25:52 UTC+1, erik@gmail.com a écrit : > On Thu, Mar 11, 2021 at 1:20 PM E.

[sage-devel] patchbot owners, please upgrade

to the latest patchbot version, namely 3.0.2 Among other details, this handles better multi-line lazy-imports. Frederic https://github.com/sagemath/sage-patchbot/releases -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this

Re: [sage-devel] issue with CRLF line endings

I have made https://trac.sagemath.org/ticket/31379 to get rid of the CRLF in these 3 files. Le jeudi 11 février 2021 à 10:43:27 UTC+1, Frédéric Chapoton a écrit : > I have been hit by this kind of annoying issue some time ago. No idea what > is happening. > There are only 3 offend

Re: [sage-devel] issue with CRLF line endings

I have been hit by this kind of annoying issue some time ago. No idea what is happening. There are only 3 offending files containing CRLF: sage$ git grep -Il $'\r' src/ src/sage/combinat/crystals/star_crystal.py src/sage/misc/element_with_label.py src/sage/rings/invariants/__init__.py We should

[sage-devel] Re: missing docker images of sagemath

----- > Illegal instruction (core dumped) > > Furthermore, all pipelines on individual branches since that date failed. > Frédéric Chapoton schrieb am Dienstag, 8. Dezember 2020 um 09:33:03 UTC+1: > >> the build for 9.3.beta3 has passed successf

[sage-devel] Re: Weird power series bug

Salut, Le code sur les espèces est connu pour être farci de bugs, et personne ne s'en est préoccupé depuis très longtemps. cf https://trac.sagemath.org/ticket/30727 Fred Le vendredi 11 décembre 2020 à 10:16:33 UTC+1, vivia...@gmail.com a écrit : > Dear all, > > I discovered a weird bug on power

[sage-devel] Re: missing docker images of sagemath

the build for 9.3.beta3 has passed successfully, so there should be a docker for that, and a docker for develop that should point to the same. https://gitlab.com/sagemath/sage/-/pipelines Frédéric Le jeudi 15 octobre 2020 à 12:09:15 UTC+2, Sébastien Labbé a écrit : > Bonjour, > > Thanks to

Re: [sage-devel] Re: Would anybody like...progress bars?

ticket for it. > If I can't get time to polish it up maybe someone else can. > > On Fri, Nov 29, 2019 at 3:51 PM Frédéric Chapoton > wrote: > > > > Hello Erik, > > > > Would you make a ticket and upload a branch on trac, please ? > > > > Frederic > &

[sage-devel] Re: Docker images

I made https://trac.sagemath.org/ticket/30960 Le mercredi 25 novembre 2020 à 11:07:09 UTC+1, Frédéric Chapoton a écrit : > now the docker building process on gitlab fails here, for the latest > develop 9.3.beta2 : > > find src/build -name '*.py' -exec rm \{\} \; > f

[sage-devel] Re: Docker images

15 novembre 2020 à 17:27:35 UTC+1, Frédéric Chapoton a écrit : > This will depend on when https://trac.sagemath.org/ticket/30874 will be > merged. > > And even still, there may be some other bad surprises in the build process > > Le dimanche 15 novembre 2020 à 09:53:11 UTC+

Re: [sage-devel] patchbots meet segmentation fault

I made https://trac.sagemath.org/ticket/30945 Le dimanche 22 novembre 2020 à 11:43:26 UTC+1, dim...@gmail.com a écrit : > On Sun, Nov 22, 2020 at 10:12 AM Frédéric Chapoton > wrote: > > > > Thanks. I agree. So what to do ? Remove the doctest ? Change the > alarm(0.5) ? &

Re: [sage-devel] patchbots meet segmentation fault

Singular. > > > > > > On Sun, Nov 22, 2020 at 8:33 AM Frédéric Chapoton > wrote: > > > > Dear all, help is required to fix the following issue. > > > > At least two patchbots, one Linux and one MacOs, meet a failure related > to pexpect interface

[sage-devel] patchbots meet segmentation fault

Dear all, help is required to fix the following issue. At least two patchbots, one Linux and one MacOs, meet a failure related to pexpect interface for singular, namely: sage -t --long --random-seed=0 src/sage/interfaces/singular.py # Killed due to segmentation fault The tested file also

[sage-devel] Re: Docker images

This will depend on when https://trac.sagemath.org/ticket/30874 will be merged. And even still, there may be some other bad surprises in the build process Le dimanche 15 novembre 2020 à 09:53:11 UTC+1, Marc Mezzarobba a écrit : > Dima Pasechnik wrote: > > hopefully everything needed to fix

[sage-devel] cocalc and sagemath webpage

Dear all, Beware that this message may be controversial. If you look at https://www.sagemath.org/ you can see four links to cocalc, one of them hidden behind the icon "sage". So, taking great care to acknowledge first all that William did and the fact that Harald is currently maintaining the

[sage-devel] Re: missing docker images of sagemath

A .gitattributes file was introduced in https://trac.sagemath.org/ticket/29733 that enforces this CRLF to LF conversion Le dimanche 8 novembre 2020 à 14:17:41 UTC+1, Frédéric Chapoton a écrit : > and this seems to be due to automatic replacement of CRLF by LF > > warn

[sage-devel] Re: missing docker images of sagemath

and this seems to be due to automatic replacement of CRLF by LF warning: CRLF will be replaced by LF in build/pkgs/planarity/patches/extern.patch. The file will have its original line endings in your working directory. Le dimanche 8 novembre 2020 à 14:09:28 UTC+1, Frédéric Chapoton a écrit

[sage-devel] Re: missing docker images of sagemath

-- saving rejects to file c/planarity.h.rej [givaro-4.1.1] Making all in gmp++ [planarity-3.0.0.5.p0] Error applying '../patches/extern.patch' Le dimanche 8 novembre 2020 à 13:56:53 UTC+1, Frédéric Chapoton a écrit : > The 9.3.beta1 build on gitlab is blocked by a failure with "planarity&

[sage-devel] Re: missing docker images of sagemath

still 4 months old. > > I notice that #30736 is in 9.3.beta0 but not #30820 yet. This should be > fixed automatically if #30820 is in the next beta? > > > On Sunday, October 25, 2020 at 8:25:46 PM UTC+1 Frédéric Chapoton wrote: > >> Could some please review https://tra

[sage-devel] help for testing #30765 ?

Hello, It would take somebody using sage with python 3.9 to check if the current branch at https://trac.sagemath.org/ticket/30765 does the job of removing a warning. Please, anybody ? Frederic -- You received this message because you are subscribed to the Google Groups "sage-devel" group.

[sage-devel] Re: missing docker images of sagemath

Could some please review https://trac.sagemath.org/ticket/30820 ? Maybe also relevant : https://trac.sagemath.org/ticket/30736 (already positive review) Le samedi 24 octobre 2020 à 09:59:00 UTC+2, Frédéric Chapoton a écrit : > I have made https://trac.sagemath.org/ticket/30820 for some sm

[sage-devel] Re: missing docker images of sagemath

:42:26 UTC+2, Frédéric Chapoton a écrit : > It seems that all pipelines are failing since 9.2.beta4. Could someone > please have a look ? > > https://gitlab.com/sagemath/sage/-/pipelines > > Le jeudi 15 octobre 2020 à 12:09:15 UTC+2, Sébastien Labbé a écrit : > >> Bonjo

[sage-devel] Re: missing docker images of sagemath

I have made https://trac.sagemath.org/ticket/30820 for some small fixes. Le samedi 24 octobre 2020 à 09:20:17 UTC+2, Frédéric Chapoton a écrit : > I can see recent tentatives from Orsay, but they failed. Maybe Erik did > launch a runner there ? > > Our .ci setting needs to be ad

[sage-devel] Re: missing docker images of sagemath

. Le vendredi 23 octobre 2020 à 20:42:26 UTC+2, Frédéric Chapoton a écrit : > It seems that all pipelines are failing since 9.2.beta4. Could someone > please have a look ? > > https://gitlab.com/sagemath/sage/-/pipelines > > Le jeudi 15 octobre 2020 à 12:09:15 UTC+2, Sébas

[sage-devel] Re: missing docker images of sagemath

It seems that all pipelines are failing since 9.2.beta4. Could someone please have a look ? https://gitlab.com/sagemath/sage/-/pipelines Le jeudi 15 octobre 2020 à 12:09:15 UTC+2, Sébastien Labbé a écrit : > Bonjour, > > Thanks to Vincent, I learned recently how to use continuous integration

[sage-devel] Re: "Real Field" -> "Real Floating-point Field"

-1, agreed with Nathan Dunfield Le mardi 20 octobre 2020 à 06:12:39 UTC+2, Nathan Dunfield a écrit : > -1: I don't really care what RealField.__repr__ returns, but cast a token > no vote to object to the logical next move of breaking backwards > compatibility by changing the meaning of

[sage-devel] sage -i fricas broken ?

Hello, it seems that "sage -i fricas" is currently not working. Maybe the tarball is missing on the mirrors, or maybe the tarball name is wrong ? Frédéric [fricas-1.3.6] FileNotMirroredError: tarball does not exist on mirror network [fricas-1.3.6]

[sage-devel] Re: A issue with the Set function in sage

Try with "set" and you will see an informative error : lists are not hashable Le jeudi 25 juin 2020 13:49:00 UTC+2, Ars-Magna a écrit : > > Is the following a bug ? > > sage: Set([[(Integer(*0*), Integer(*0*)), (Integer(*1*), Integer(*1* > ))],[(Integer(*0*), Integer(*0*)), (Integer(*1*),

[sage-devel] Re: FTP mirrors' HTML is downloaded instead of rendered in Chromium / Chrome

I have made a pull request https://github.com/sagemath/website/pull/188 Le samedi 11 avril 2020 13:16:37 UTC+2, Ricardo Buring a écrit : > > Dear sage-devel, > > on the downloads page http://www.sagemath.org/download.html there are > links to several mirrors, and one of them (FU Berlin) uses

[sage-devel] how to call compiled pari script from sage ?

Hello, I have a small .gp file, that I am using from inside sage, and that works fine. I can compile it and use it from pari/gp using "gp2c-run" and it works fine there. But when I try to use the compiled file (more precisely the ".so") from sage by using "pari.install" with the lines

[sage-devel] Re: Working on Ticket 13649. Can't find a _cache_an_element() declaration.

> git grep -c "cache_an_element" src/sage src/sage/rings/number_field/number_field.py:1 src/sage/structure/parent.pxd:1 src/sage/structure/parent.pyx:4 src/sage/structure/parent_old.pyx:4 Le mercredi 26 février 2020 11:09:11 UTC+1, Sagnik Dey a écrit : > > I want to understand the code related

[sage-devel] Re: drop python2 compatibility in 9.1 ?

nvier 2020 20:44:10 UTC+1, Frédéric Chapoton a écrit : > > Hello, > > I would like to suggest that the sooner we drop Python 2 support the > better. We still need to handle the upgrade to ipython7 and the > compatibility with python 3.8. All this will be made very difficult

[sage-devel] Re: Build of 9.0 failed at R

If you repeat "make build -j4" until this is the only failure, this does not prevent sage to work. So if you do not need R, you can ignore that. I have the same problem on several machine with Ubuntu 19.10 F Le samedi 11 janvier 2020 16:18:37 UTC+1, Malcolm MacCallum a écrit : > > I am using

[sage-devel] Re: drop python2 compatibility in 9.1 ?

the wiki promise was written by myself alone, and I think it should be changed. I think there will be very few (or no) people that will desire to compile sage 9.0 with python 2. And 9.1 even more. People that want to be up to date do not care about py2. I therefore strongly vote for the

[sage-devel] drop python2 compatibility in 9.1 ?

Hello, I would like to suggest that the sooner we drop Python 2 support the better. We still need to handle the upgrade to ipython7 and the compatibility with python 3.8. All this will be made very difficult if we insist on maintaining a codebase that is both compatible with python 2 and

[sage-devel] Re: Problems setting patchbots

Apparenlty, the # symbol was (at least part of) the problem. I pushed a fix a few minutes ago, not yet tested. You can git pull the latest patchbot sources. F Le mardi 17 décembre 2019 16:55:27 UTC+1, mmarco a écrit : > > >> The second may be a bug in the patchbot server itself. I have no time

Re: [sage-devel] Re: mad patchbot?

to be > banned. > > > On Fri, 6 Dec 2019, 07:57 Frédéric Chapoton, > wrote: > >> The mad patchbot named "sage4" is still running at full steam, sending >> wrong reports by hundreds. >> >> It seems to be running an old version ot the patchbot code on p

[sage-devel] Re: Problems setting patchbots

The first problem is a known one, you can uninstall gap_packages to fix it. The second may be a bug in the patchbot server itself. I have no time to investigate. Maybe the # in the patchbot name is not a good idea (random guess) ? F Le vendredi 6 décembre 2019 13:04:06 UTC+1, mmarco a écrit :

[sage-devel] Re: mad patchbot?

The mad patchbot named "sage4" is still running at full steam, sending wrong reports by hundreds. It seems to be running an old version ot the patchbot code on python 2.7, which is not allowed anymore. Frederic Le lundi 2 décembre 2019 15:27:39 UTC+1, Léo Brunswic a écrit : > > Hi , > > I

[sage-devel] Re: Would anybody like...progress bars?

Hello Erik, Would you make a ticket and upload a branch on trac, please ? Frederic Le jeudi 23 mai 2019 18:41:04 UTC+2, E. Madison Bray a écrit : > > Something I've wanted for a long time in the Sage doctest runner is > progress bars, so I hacked up a prototype (see screenshot). It works >

[sage-devel] Re: SageNB broken because of stmp???

Yes. *No sagenb in Python3*. The current stumbling point is that sagenb uses twisted and twisted is not py3 compatible, despite pretending to be so. I did make some lonely efforts to make sagenb work with py3. This stopped on the error message that you give. Frederic Le samedi 23 novembre

[sage-devel] to all patchbot breeders : urgent care required

Hello Due to the *switch to python3* in sage 9.0.beta6, all patchbots are broken right now, unless they were already running python3. So everybody running a patchbot must stop their patchbot, make distclean and start them from fresh on top of sage 9.0.beta6 If you want to go on running a

[sage-devel] Re: Switch to Python 3 by default

Could please some of the many plus-one-ing people try the branch at #28660 and report there if it works for them, namely builds a working python3-sage by default ? Frédéric Le dimanche 27 octobre 2019 01:58:23 UTC+2, Volker Braun a écrit : > > Maybe I missed it, but I didn't find a ticket for

[sage-devel] Re: Switch to Python 3 by default

Please feel free to edit and enhance the wiki page about the switch : https://wiki.sagemath.org/Python3-Switch Le dimanche 27 octobre 2019 01:58:23 UTC+2, Volker Braun a écrit : > > Maybe I missed it, but I didn't find a ticket for that. I think now would > be a good time to flip the switch,

[sage-devel] Re: sage and emacs (and unicode)

Did you try to change the font in emacs until finding a correct font with constant width ? Le mardi 22 octobre 2019 12:22:43 UTC+2, Martin R a écrit : > > This is, superficially, a support question for a minor problem with emacs > and sage-shell-mode (and therefore possibly off topic, please

[sage-devel] Re: quadratic forms signature_vector() gives different results for real cyclotomics and for reals

The bug over the cyclotomic field is caused by sage: K = CyclotomicField(8) sage: K(-1/16) > 0 True Le vendredi 18 octobre 2019 13:24:51 UTC+2, Frédéric Chapoton a écrit : > > This works (in sage 8.9) when using > > K.=QuadraticField(2) > > > > Le vendredi 18

[sage-devel] Re: quadratic forms signature_vector() gives different results for real cyclotomics and for reals

This works (in sage 8.9) when using K.=QuadraticField(2) Le vendredi 18 octobre 2019 02:12:02 UTC+2, Ignat Soroko a écrit : > > I am computing the signature of a quadratic form having entries 0, 1, > -1/2, -sqrt(2)/2. I noticed that the result of signature_vector() is > different if we treat

  1   2   3   4   5   6   >