[sage-devel] Re: sensational bug!

[Frédéric Chapoton]

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 --long --random-seed=286735480429121101562228604801325644303 
> src/sage/rings/tests.py 
> ** 
> Error: Failed example:: Got: Random testing has revealed a problem in 
> test_karatsuba_multiplication 
> Please report this bug! You may be the first 
> person in the world to have seen this problem. 
> Please include this random seed in your bug report: 
> Random seed: 305806809989734915896642073966608392384 
> ValueError('Multiplication failed') 
> test_karatsuba_multiplication(QQbar, 3, 3, numtests=2) # long time, needs 
> sage.rings.number_field 
> Expected nothing 
> Got: 
> Random testing has revealed a problem in test_karatsuba_multiplication 
> Please report this bug! You may be the first 
> person in the world to have seen this problem. 
> Please include this random seed in your bug report: 
> Random seed: 305806809989734915896642073966608392384 
> ValueError('Multiplication failed')

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/7021ce25-f9a3-4c2e-a176-f109e9079d6an%40googlegroups.com.

[sage-devel] doctest logs are unusable

[Frédéric Chapoton]

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.modules'} 
21 
optional
 
tags: {'sage.modules'} 
22 
optional
 
tags: {'sage.modules'} 
23 
optional
 
tags: {'sage.modules'} 
24 
optional
 
tags: {'sage.modules'} 
25 
optional
 
tags: {'sage.modules'} 
26 
optional
 
tags: {'sage.modules'} 
27 
optional
 
tags: {'sage.modules'}

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/5107dd4e-76df-4cf3-8a11-270ab37ed9een%40googlegroups.com.

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

[Frédéric Chapoton]

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.
>
> (1) There are two many checks. I have to scroll.
> (2) Some checks look similar. I have to think to see which one is 
> significant.
> (3) They are not sorted. I don't know the order.
> (4) Some checks are cancelled or skipped. I don't know why or what to do 
> with them.
> (5) Some checks are broken at the base. I have to check the check.
>
> I started to ignore them and  to check the PR branches on my own system 
> locally, as in the old days.
>
> Any idea to improve the situation?
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f311a861-4b7c-4e2d-9c54-c29b879d72c0n%40googlegroups.com.

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

[Frédéric Chapoton]

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 many doctests 
checking for coercion failure now report coercion success. There are still 
a few problematic things to solve, in particular about infinite polynomials 
rings.

Please express your opinion about that change of behaviour. 

Frederic

Question: what does magma do ?

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/130fadf1-6308-4d6b-8607-a0f6ca22d76bn%40googlegroups.com.

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

[Frédéric Chapoton]

yes, stable versions would be good enough. And not too much work, 
hopefully. So, please ask Julian to be added to the sagemath organisation 
on dockerhub.

Frederic

Le dimanche 16 juillet 2023 à 13:38:47 UTC+2, seb@gmail.com a écrit :

>
> I successfully built one for stable 10.0, two weeks ago using the current 
> version of the docker/Dockerfile following the instructions given there 
> (in section HOWTO use this file to manually create new images for Docker 
> Hub). I haven't really used it yet. However, Sage 10.0 starts and works 
> unless you try to use IPython magics (for example ? to read the 
> documentation). If you do that, it crashes (but so does the 9.7 image). 
> Yesterday I pushed that to my private Docker account. Therefore, for the 
> time being it can be used at your own risk via docker run -it 
> soehms/sagemath:10.0. I can try to do the same for 9.8.
>
> Frederic, would a restriction to the stable versions be acceptable to you? 
> I would like to have a continuation of the Docker images, too. But I can 
> relinquish development versions since for this use case there are other 
> alternatives, such as Gitpod. 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 
>> up-to-date docker images on dockerhub ?
>>
>> Frederic
>>
>> Le jeudi 11 mai 2023 à 15:32:28 UTC+2, julian...@fsfe.org a écrit :
>>
>>> Btw., I recently applied for "Sponsored OSS" status on the Docker Hub 
>>> which was finally granted. So we can now have more then 3 user accounts 
>>> with write access (until now it was mkoeppe, a bot user and myself.) Please 
>>> contact me if you want to be added as a maintainer.
>>>
>>> On Thursday, May 11, 2023 at 4:29:31 PM UTC+3 julian...@fsfe.org wrote:
>>>
>>>> Sorry, I didn't see this thread.
>>>>
>>>> I do have the credentials for docker hub. I am happy to share them with 
>>>> anybody who wants to help with maintaining the docker images. (I don't use 
>>>> the docker images anymore myself so I do not really maintain them anymore. 
>>>> Also, the automatic infrastructure that we used to update them broke years 
>>>> ago which makes the process quite a bit of work. With each release 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.)
>>>>
>>>> julian
>>>>
>>>> On Thursday, May 11, 2023 at 3:27:20 PM UTC+3 Frédéric Chapoton wrote:
>>>>
>>>>> 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 ? 
>>>>>> 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 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 subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/dd4e7124-b36a-4893-820d-83ea919cc656n%40googlegroups.com.

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

[Frédéric Chapoton]

Hello,

Anybody with some docker expertise who would like to help us having 
up-to-date docker images on dockerhub ?

Frederic

Le jeudi 11 mai 2023 à 15:32:28 UTC+2, julian...@fsfe.org a écrit :

> Btw., I recently applied for "Sponsored OSS" status on the Docker Hub 
> which was finally granted. So we can now have more then 3 user accounts 
> with write access (until now it was mkoeppe, a bot user and myself.) Please 
> contact me if you want to be added as a maintainer.
>
> On Thursday, May 11, 2023 at 4:29:31 PM UTC+3 julian...@fsfe.org wrote:
>
>> Sorry, I didn't see this thread.
>>
>> I do have the credentials for docker hub. I am happy to share them with 
>> anybody who wants to help with maintaining the docker images. (I don't use 
>> the docker images anymore myself so I do not really maintain them anymore. 
>> Also, the automatic infrastructure that we used to update them broke years 
>> ago which makes the process quite a bit of work. With each release 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.)
>>
>> julian
>>
>> On Thursday, May 11, 2023 at 3:27:20 PM UTC+3 Frédéric Chapoton wrote:
>>
>>> 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 ? 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 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 subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/91380723-eef0-44f5-b13d-9a6142c3edf0n%40googlegroups.com.

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

[Frédéric Chapoton]

I have zero experience with docker images (never used one, never built 
one). So I would rather let the task to somebody more knowledgeable in the 
matter.

Better to automatize of course, but at least one could manually make images 
for 9.8 and 10.0 so that people can use them soon.

Frederic

Le jeudi 11 mai 2023 à 15:32:04 UTC+2, Edgar Costa a écrit :

> I realized that one of my messages never got to the mailing list.
>
> If we agree that we would like to keep having this, then we should move 
>> the old gitlab workflow to GitHub.
>> I have minimal experience building dockers, but these are quite 
>> convenient when you suddenly break your sage due to some external library 
>> upgrade or when you are trying to use a code that was written for a version 
>> of the past.
>>
>
> I am happy to help with maintaining the docker images.
> But maybe first I should try to build them myself :)
>
> On Thu, May 11, 2023 at 9:29 AM julian...@fsfe.org  
> wrote:
>
>> Sorry, I didn't see this thread.
>>
>> I do have the credentials for docker hub. I am happy to share them with 
>> anybody who wants to help with maintaining the docker images. (I don't use 
>> the docker images anymore myself so I do not really maintain them anymore. 
>> Also, the automatic infrastructure that we used to update them broke years 
>> ago which makes the process quite a bit of work. With each release 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.)
>>
>> julian
>>
>> On Thursday, May 11, 2023 at 3:27:20 PM UTC+3 Frédéric Chapoton wrote:
>>
>>> 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 ? 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 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 subscribed to the Google Groups 
>> "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to sage-devel+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/a3d93928-3b4f-4ed1-a5ed-e29aa2275d72n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/sage-devel/a3d93928-3b4f-4ed1-a5ed-e29aa2275d72n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/ba32e83c-06f2-4593-8201-600802187dcdn%40googlegroups.com.

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

[Frédéric Chapoton]

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 ? 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 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 subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/46326268-9d68-4d69-a3b9-75740674a215n%40googlegroups.com.

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

[Frédéric Chapoton]

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 from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e241fb17-113d-4345-b931-c413827eda98n%40googlegroups.com.

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

[Frédéric Chapoton]

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 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 subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/943fb1a2-ca98-4829-bf0f-deb9ca01c704n%40googlegroups.com.

[sage-devel] images lacking on docker hub

[Frédéric Chapoton]

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 subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/b8402a89-e866-463f-ae16-ecde1b4e2b8an%40googlegroups.com.

[sage-devel] patchbots off

[Frédéric Chapoton]

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 to turn them to runners in our new setting, but please do not ask me 
how.
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 from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/096df874-34b6-4956-ab53-e249e4d0f658n%40googlegroups.com.

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

[Frédéric Chapoton]

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)  -
 2
x  + 1
Le mercredi 2 novembre 2022 à 04:04:54 UTC+1, pvit...@gmail.com a écrit :

> Thanks a lot. I forgot to post it here
> El martes, 1 de noviembre de 2022 a las 12:01:33 UTC+1, kcrisman escribió:
>
>> please post here the link to your report
>>>

>> https://sourceforge.net/p/maxima/bugs/4037/ 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/16c8c87c-96cd-46d3-bfa5-ac44c650a6fcn%40googlegroups.com.

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

[Frédéric Chapoton]

amusingly, one can see that some power of 2 is lurking around :

(%i36) expand(diff(integrate(x*log(x)**13/(1+x**2),x),x));
  13
4096 x log  (x)
(%o36)  ---
  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ó:
>
>> The factor-2 problem is also present for the integral with no bounds. 
>> Please report in maxima's bug reporting site.
>>
>> (%i20) integrate(x*log(x)^4/(x^2 + 1),x);
>>  4 2
>> 2 log (x) log(x  + 1)   22
>> (%o20) - (3 ((- -) + li (- x ) - 2 log(x) li (- x )
>>   354
>>  3   2
>> 4 log (x) li (- x 
>> )
>>2   22
>> + 2 log (x) li (- x ) - 
>> ---))/2
>>   3  3
>> (%i21) diff(%,x);  
>>  4
>>   2 x log (x)
>> (%o21)---
>>  2
>> x  + 1
>>
>> Le mardi 25 octobre 2022 à 00:17:07 UTC+2, pvit...@gmail.com a écrit :
>>
>>> Thank you very much for the analysis. If I understand correctly, the bug 
>>> is in this part of the integral:  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 
>>> escribió:
>>>
>>>> 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), x,0,1).n()
>>>>> 1.45817965567036
>>>>> sage: (x*log(x)^4/(x^2 + 1)).nintegral(x,0,1)
>>>>> (0.7290898278351722, 2.48288156701193e-09, 357, 0)
>>>>> sage: integrate(-log(x)^4/(x^2 + 1), x,0,1).n()
>>>>> -23.9077878738501
>>>>> sage: (-log(x)^4/(x^2 + 1)).nintegral(x,0,1)
>>>>> (-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)
>>>>>> -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: aa.nintegral(x,0,1)
>>>>>> (-11.58934902297507, 5.068708119893017e-08, 525, 0)
>>>>>> sage: bb.nintegral(x,0,1)
>>>>>> (11.66543724536065, 4.943314557692702e-08, 525, 0)
>>>>>> sage: integral(aa,x,0,1).n()
>>>>>> -11.2248041090899
>>>>>> sage: integral(bb,x,0,1).n()
>>>>>> 11.6654372453629
>>>>>>
>>>>>>
>>>>>>
>>>>>> Le lundi 24 octobre 2022 à 00:14:09 UTC+2, pvit...@gmail.com a 
>>>>>> écrit :
>>>>>>
>>>>>>> I am using Sage 9.7 running in Arch linux over WSL2
>>>>>>>
>>>>>>> I get different results for an integral using numerical integration 
>>>>>>> (which seems to agree with Mathematica) and symbolic integration:
>>>>>>>
>>>>>>> numerical_integral(x^2*(log(x))^4/((x+1)*(1+x^2)),0,1)
>>>>>>> (0.07608822217400527, 1.981757967172001e-07)
>>>>>>>
>>>>>>> integral(x^2*(log(x))^4/((x+1)*(1+x^2)),x,0,1)
>>>>>>> 6*I*polylog(5, I) - 6*I*polylog(5, -I) + 765/64*zeta(5)
>>>>>>> integral(x^2*(log(x))^4/((x+1)*(1+x^2)),x,0,1).n()
>>>>>>> 0.440633136273036
>>>>>>>
>>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/adaae847-3c95-4c29-b21b-091400cd2746n%40googlegroups.com.

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

[Frédéric Chapoton]

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 problem is also present for the integral with no bounds. 
>> Please report in maxima's bug reporting site.
>>
>> (%i20) integrate(x*log(x)^4/(x^2 + 1),x);
>>  4 2
>> 2 log (x) log(x  + 1)   22
>> (%o20) - (3 ((- -) + li (- x ) - 2 log(x) li (- x )
>>   354
>>  3   2
>> 4 log (x) li (- x 
>> )
>>2   22
>> + 2 log (x) li (- x ) - 
>> ---))/2
>>   3  3
>> (%i21) diff(%,x);  
>>  4
>>   2 x log (x)
>> (%o21)---
>>  2
>> x  + 1
>>
>> Le mardi 25 octobre 2022 à 00:17:07 UTC+2, pvit...@gmail.com a écrit :
>>
>>> Thank you very much for the analysis. If I understand correctly, the bug 
>>> is in this part of the integral:  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 
>>> escribió:
>>>
>>>> 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), x,0,1).n()
>>>>> 1.45817965567036
>>>>> sage: (x*log(x)^4/(x^2 + 1)).nintegral(x,0,1)
>>>>> (0.7290898278351722, 2.48288156701193e-09, 357, 0)
>>>>> sage: integrate(-log(x)^4/(x^2 + 1), x,0,1).n()
>>>>> -23.9077878738501
>>>>> sage: (-log(x)^4/(x^2 + 1)).nintegral(x,0,1)
>>>>> (-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)
>>>>>> -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: aa.nintegral(x,0,1)
>>>>>> (-11.58934902297507, 5.068708119893017e-08, 525, 0)
>>>>>> sage: bb.nintegral(x,0,1)
>>>>>> (11.66543724536065, 4.943314557692702e-08, 525, 0)
>>>>>> sage: integral(aa,x,0,1).n()
>>>>>> -11.2248041090899
>>>>>> sage: integral(bb,x,0,1).n()
>>>>>> 11.6654372453629
>>>>>>
>>>>>>
>>>>>>
>>>>>> Le lundi 24 octobre 2022 à 00:14:09 UTC+2, pvit...@gmail.com a 
>>>>>> écrit :
>>>>>>
>>>>>>> I am using Sage 9.7 running in Arch linux over WSL2
>>>>>>>
>>>>>>> I get different results for an integral using numerical integration 
>>>>>>> (which seems to agree with Mathematica) and symbolic integration:
>>>>>>>
>>>>>>> numerical_integral(x^2*(log(x))^4/((x+1)*(1+x^2)),0,1)
>>>>>>> (0.07608822217400527, 1.981757967172001e-07)
>>>>>>>
>>>>>>> integral(x^2*(log(x))^4/((x+1)*(1+x^2)),x,0,1)
>>>>>>> 6*I*polylog(5, I) - 6*I*polylog(5, -I) + 765/64*zeta(5)
>>>>>>> integral(x^2*(log(x))^4/((x+1)*(1+x^2)),x,0,1).n()
>>>>>>> 0.440633136273036
>>>>>>>
>>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/4f1ac638-729a-4633-9684-547dca616306n%40googlegroups.com.

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

[Frédéric Chapoton]

The factor-2 problem is also present for the integral with no bounds. 
Please report in maxima's bug reporting site.

(%i20) integrate(x*log(x)^4/(x^2 + 1),x);
 4 2
2 log (x) log(x  + 1)   22
(%o20) - (3 ((- -) + li (- x ) - 2 log(x) li (- x )
  354
 3   2
4 log (x) li (- x )
   2   22
+ 2 log (x) li (- x ) - 
---))/2
  3  3
(%i21) diff(%,x);  
 4
  2 x log (x)
(%o21)---
 2
x  + 1

Le mardi 25 octobre 2022 à 00:17:07 UTC+2, pvit...@gmail.com a écrit :

> Thank you very much for the analysis. If I understand correctly, the bug 
> is in this part of the integral:  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 
> escribió:
>
>> 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), x,0,1).n()
>>> 1.45817965567036
>>> sage: (x*log(x)^4/(x^2 + 1)).nintegral(x,0,1)
>>> (0.7290898278351722, 2.48288156701193e-09, 357, 0)
>>> sage: integrate(-log(x)^4/(x^2 + 1), x,0,1).n()
>>> -23.9077878738501
>>> sage: (-log(x)^4/(x^2 + 1)).nintegral(x,0,1)
>>> (-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)
>>>> -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: aa.nintegral(x,0,1)
>>>> (-11.58934902297507, 5.068708119893017e-08, 525, 0)
>>>> sage: bb.nintegral(x,0,1)
>>>> (11.66543724536065, 4.943314557692702e-08, 525, 0)
>>>> sage: integral(aa,x,0,1).n()
>>>> -11.2248041090899
>>>> sage: integral(bb,x,0,1).n()
>>>> 11.6654372453629
>>>>
>>>>
>>>>
>>>> Le lundi 24 octobre 2022 à 00:14:09 UTC+2, pvit...@gmail.com a écrit :
>>>>
>>>>> I am using Sage 9.7 running in Arch linux over WSL2
>>>>>
>>>>> I get different results for an integral using numerical integration 
>>>>> (which seems to agree with Mathematica) and symbolic integration:
>>>>>
>>>>> numerical_integral(x^2*(log(x))^4/((x+1)*(1+x^2)),0,1)
>>>>> (0.07608822217400527, 1.981757967172001e-07)
>>>>>
>>>>> integral(x^2*(log(x))^4/((x+1)*(1+x^2)),x,0,1)
>>>>> 6*I*polylog(5, I) - 6*I*polylog(5, -I) + 765/64*zeta(5)
>>>>> integral(x^2*(log(x))^4/((x+1)*(1+x^2)),x,0,1).n()
>>>>> 0.440633136273036
>>>>>
>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/9e1d643a-39d7-4c35-8d8f-d2bc48d708c1n%40googlegroups.com.

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

[Frédéric Chapoton]

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), x,0,1).n()
> 1.45817965567036
> sage: (x*log(x)^4/(x^2 + 1)).nintegral(x,0,1)
> (0.7290898278351722, 2.48288156701193e-09, 357, 0)
> sage: integrate(-log(x)^4/(x^2 + 1), x,0,1).n()
> -23.9077878738501
> sage: (-log(x)^4/(x^2 + 1)).nintegral(x,0,1)
> (-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)
>> -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: aa.nintegral(x,0,1)
>> (-11.58934902297507, 5.068708119893017e-08, 525, 0)
>> sage: bb.nintegral(x,0,1)
>> (11.66543724536065, 4.943314557692702e-08, 525, 0)
>> sage: integral(aa,x,0,1).n()
>> -11.2248041090899
>> sage: integral(bb,x,0,1).n()
>> 11.6654372453629
>>
>>
>>
>> Le lundi 24 octobre 2022 à 00:14:09 UTC+2, pvit...@gmail.com a écrit :
>>
>>> I am using Sage 9.7 running in Arch linux over WSL2
>>>
>>> I get different results for an integral using numerical integration 
>>> (which seems to agree with Mathematica) and symbolic integration:
>>>
>>> numerical_integral(x^2*(log(x))^4/((x+1)*(1+x^2)),0,1)
>>> (0.07608822217400527, 1.981757967172001e-07)
>>>
>>> integral(x^2*(log(x))^4/((x+1)*(1+x^2)),x,0,1)
>>> 6*I*polylog(5, I) - 6*I*polylog(5, -I) + 765/64*zeta(5)
>>> integral(x^2*(log(x))^4/((x+1)*(1+x^2)),x,0,1).n()
>>> 0.440633136273036
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f0487f49-d1a4-47f5-8ef1-7983a13ccfb9n%40googlegroups.com.

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

[Frédéric Chapoton]

and one more step :

sage: integrate(x*log(x)^4/(x^2 + 1), x,0,1).n()
1.45817965567036
sage: (x*log(x)^4/(x^2 + 1)).nintegral(x,0,1)
(0.7290898278351722, 2.48288156701193e-09, 357, 0)
sage: integrate(-log(x)^4/(x^2 + 1), x,0,1).n()
-23.9077878738501
sage: (-log(x)^4/(x^2 + 1)).nintegral(x,0,1)
(-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)
> -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: aa.nintegral(x,0,1)
> (-11.58934902297507, 5.068708119893017e-08, 525, 0)
> sage: bb.nintegral(x,0,1)
> (11.66543724536065, 4.943314557692702e-08, 525, 0)
> sage: integral(aa,x,0,1).n()
> -11.2248041090899
> sage: integral(bb,x,0,1).n()
> 11.6654372453629
>
>
>
> Le lundi 24 octobre 2022 à 00:14:09 UTC+2, pvit...@gmail.com a écrit :
>
>> I am using Sage 9.7 running in Arch linux over WSL2
>>
>> I get different results for an integral using numerical integration 
>> (which seems to agree with Mathematica) and symbolic integration:
>>
>> numerical_integral(x^2*(log(x))^4/((x+1)*(1+x^2)),0,1)
>> (0.07608822217400527, 1.981757967172001e-07)
>>
>> integral(x^2*(log(x))^4/((x+1)*(1+x^2)),x,0,1)
>> 6*I*polylog(5, I) - 6*I*polylog(5, -I) + 765/64*zeta(5)
>> integral(x^2*(log(x))^4/((x+1)*(1+x^2)),x,0,1).n()
>> 0.440633136273036
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/06fc8cdf-6742-424c-b2c2-7559aaf08934n%40googlegroups.com.

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

[Frédéric Chapoton]

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: aa.nintegral(x,0,1)
(-11.58934902297507, 5.068708119893017e-08, 525, 0)
sage: bb.nintegral(x,0,1)
(11.66543724536065, 4.943314557692702e-08, 525, 0)
sage: integral(aa,x,0,1).n()
-11.2248041090899
sage: integral(bb,x,0,1).n()
11.6654372453629



Le lundi 24 octobre 2022 à 00:14:09 UTC+2, pvit...@gmail.com a écrit :

> I am using Sage 9.7 running in Arch linux over WSL2
>
> I get different results for an integral using numerical integration (which 
> seems to agree with Mathematica) and symbolic integration:
>
> numerical_integral(x^2*(log(x))^4/((x+1)*(1+x^2)),0,1)
> (0.07608822217400527, 1.981757967172001e-07)
>
> integral(x^2*(log(x))^4/((x+1)*(1+x^2)),x,0,1)
> 6*I*polylog(5, I) - 6*I*polylog(5, -I) + 765/64*zeta(5)
> integral(x^2*(log(x))^4/((x+1)*(1+x^2)),x,0,1).n()
> 0.440633136273036
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/6505b463-2d26-4427-8c07-6000230cb556n%40googlegroups.com.

[sage-devel] BROADCAST : Trac maintenance

[Frédéric Chapoton]

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 inconvience, and thanks for your patience. We are getting 
close.

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 from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/79031119-f0bd-49bd-a36e-846b01e819d1n%40googlegroups.com.

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

[Frédéric Chapoton]

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)
[sagelib-9.7.rc1] Installing collected packages: sagemath-standard
[sagelib-9.7.rc1]   Attempting uninstall: sagemath-standard
[sagelib-9.7.rc1] WARNING: Ignoring invalid distribution 
-agemath-standard 
(/home/.../sage/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages)

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/5f50829e-115b-4e18-bf1e-064362c195b0n%40googlegroups.com.

[sage-devel] Re: BROADCAST MESSAGE

[Frédéric Chapoton]

I can still modify the comments. It may be a matter of permissions. If 
somebody else confirms, one will have to check.

Le jeudi 8 septembre 2022 à 01:06:59 UTC+2, John H Palmieri a écrit :

> Let me echo everyone's thanks to the people who worked/are working on the 
> upgrade.
>
> A question: I don't see a way to edit my comments on trac tickets. Is that 
> feature gone? (If it is, I don't mind, I just want to make sure I'm not 
> missing something obvious.)
>
> -- 
> John
>
>
> On Wednesday, September 7, 2022 at 7:25:11 AM UTC-7 Travis Scrimshaw wrote:
>
>> Thank you to everyone who has worked on getting this fixed and working 
>> again. A big special thanks to Frédéric for taking point (or at least 
>> willing to do the public relations).
>>
>> Best,
>> Travis
>>
>> On Monday, September 5, 2022 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 
>>> écrit :
>>>
>>>> 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!
>>>>
>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d1fe0de5-ae7f-4a12-ad17-d680502bcb76n%40googlegroups.com.

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

[Frédéric Chapoton]

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 
> to set up the ssh key again, but I was not able to find SSH Key in sage 
> preference. I'm wondering if anyone knows where I can update the ssh key or 
> if there is anything I could do to fix the permission denied. Thank you so 
> much for any help in advance!
>
> Sincerely,
> Yueqi Li
> [image: Screen Shot 2022-09-05 at 9.58.38 PM.png][image: Screen Shot 
> 2022-09-05 at 9.53.35 PM.png]
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f4ac7364-6b88-405f-937b-bdfe572d9546n%40googlegroups.com.

[sage-devel] Re: BROADCAST MESSAGE

[Frédéric Chapoton]

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!

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/cd35c3ab-2330-46cf-9bc6-36ecc08a005dn%40googlegroups.com.

[sage-devel] BROADCAST MESSAGE

[Frédéric Chapoton]

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, and thanks for your patience.

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 from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/be724f9f-054f-4f0b-ae9b-b626aec2587cn%40googlegroups.com.

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

[Frédéric Chapoton]

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 
> machine? 
>
>
>
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/fde252fc-d96c-4f31-a76a-e61eef566e89n%40googlegroups.com.

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

[Frédéric Chapoton]

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 repairable and there is not urgent need to move to 
gitlab. It would be good to get help from Erik M Bray, but he has not 
answered my last mail.
F

Le vendredi 2 septembre 2022 à 07:22:51 UTC+2, Matthias Koeppe a écrit :

> Hence nothing has run on GH Actions for 2 days
> https://github.com/sagemath/sagetrac-mirror/actions
>
> Is this being worked on?
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/b40f9d0a-c72a-4243-96d3-3a0d660b872an%40googlegroups.com.

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

[Frédéric Chapoton]

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 this is related with the recent restart of Trac: the ticket numbers 
> in the "Dependencies" field of a ticket are no longer clickable, nor 
> colored. An example is
> https://trac.sagemath.org/ticket/30229
>
> Eric.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/16645fbc-b54c-473c-8858-38de1e15513bn%40googlegroups.com.

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

[Frédéric Chapoton]

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
>   - suggest that someone else rolls back ?
>
> In either case, as of 11:23 CET, still no access from a different machine 
> (SSH key not yet updated)..
>  
>
>>
>> On Wed, 31 Aug 2022, 08:01 Kwankyu Lee,  wrote:
>>
>>> This seems a different problem. The website is not accessible.
>>>
>>> On Wednesday, August 31, 2022 at 3:48:19 PM UTC+9 dim...@gmail.com 
>>> wrote:
>>>
 new ssh keys on the server, don't know how to tell this to "git trac"

 On Wed, 31 Aug 2022, 07:45 Emmanuel Charpentier, <
 emanuel.c...@gmail.com> wrote:

> This morning (Aug 31, 2022, 8:43), any attempt to reach `
> trac.sagemath.org` ends up displayong a Python trace :
>
> ```
> Traceback (most recent call last): File 
> "/usr/local/lib/python2.7/dist-packages/trac/web/api.py", line 602, in 
> send_error data, 'text/html') File 
> "/usr/local/lib/python2.7/dist-packages/trac/web/chrome.py", line 1104, 
> in 
> render_template template = self.load_template(filename, method=method) 
> File 
> "/usr/local/lib/python2.7/dist-packages/trac/web/chrome.py", line 1053, 
> in 
> load_template self.get_all_templates_dirs(), 
> auto_reload=self.auto_reload, 
> File "/usr/local/lib/python2.7/dist-packages/trac/web/chrome.py", line 
> 758, 
> in get_all_templates_dirs for provider in self.template_providers: File 
> "/usr/local/lib/python2.7/dist-packages/trac/core.py", line 82, in 
> extensions components = [component.compmgr[cls] for cls in classes] File 
> "/usr/local/lib/python2.7/dist-packages/trac/core.py", line 208, in 
> __getitem__ component = cls(self) File 
> "/usr/local/lib/python2.7/dist-packages/trac/core.py", line 144, in 
> __call__ self.__init__() File 
> "/usr/local/lib/python2.7/dist-packages/sage_trac/sshkeys.py", line 195, 
> in 
> __init__ self._init_gitolite_admin() File 
> "/usr/local/lib/python2.7/dist-packages/sage_trac/sshkeys.py", line 66, 
> in 
> wrapper ret = inner_wrapper(self, *args, **kwargs) File 
> "/usr/local/lib/python2.7/dist-packages/fasteners/lock.py", line 302, in 
> wrapper return f(self, *args, **kwargs) File 
> "/usr/local/lib/python2.7/dist-packages/sage_trac/sshkeys.py", line 52, 
> in 
> inner_method return method(self, *args, **kwargs) File 
> "/usr/local/lib/python2.7/dist-packages/sage_trac/sshkeys.py", line 226, 
> in 
> _init_gitolite_admin self._update_gitolite_admin() File 
> "/usr/local/lib/python2.7/dist-packages/sage_trac/sshkeys.py", line 287, 
> in 
> _update_gitolite_admin 'repository'.format(out)) TracError: Error 
> updating 
> the gitolite-admin repository: Host key verification failed. fatal: Could 
> not read from remote repository. Please make sure you have the correct 
> access rights and the repository exists. ; you may have to manually clean 
> up or re-clone the repository
> ```
>
> Any idea ?
>
> -- 
> You received this message because you are subscribed to the Google 
> Groups "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to sage-devel+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/0c956548-4fa6-4970-8662-84de5b6975f0n%40googlegroups.com
>  
> 
> .
>
 -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "sage-devel" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to sage-devel+...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-devel/4a798658-f64e-4931-859d-570459789fc7n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/00458692-b599-45a6-b02c-067f77eedd98n%40googlegroups.com.

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

[Frédéric Chapoton]

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 take less time than scheduled.

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 from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/5e902ce6-a035-44ad-ba88-54ba67a9c893n%40googlegroups.com.

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

[Frédéric Chapoton]

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 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 to do with "editable-inplace" or 
> "virtual-env" ?
> Frederic
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/305f6721-d44b-48c8-99ac-5d6f69b719c0n%40googlegroups.com.

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

[Frédéric Chapoton]

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 to do with "editable-inplace" or 
"virtual-env" ?
Frederic

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/2522f787-0a99-4295-b1e1-162462ff03f0n%40googlegroups.com.

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

[Frédéric Chapoton]

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 a more recent os, with a more recent ssh ?

The ssh log indicates that there is some incompatibility :

debug1: send_pubkey_test: no mutual signature algorithm

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 from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a3131849-6c55-46ae-adf4-412b734131abn%40googlegroups.com.

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

[Frédéric Chapoton]

you can use the base argument in the https adress

https://patchbot.sagemath.org/ticket/0/?base=9.5.rc1

But sometimes I clean old reports, keeping only very recent ones

Le samedi 22 janvier 2022 à 14:54:40 UTC+1, Samuel Lelievre a écrit :

> Hi Frédéric,
>
> Thanks for the link! Hope the branch at that ticket gets
> merged in the next development release. Tried building
> Sage 9.5.rc3 but hit the sagemath_doc_html build failure
> reported at ticket #33139.
>
> Are the reports at https://patchbot.sagemath.org/ticket/0/
> only visible until the next development 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 
> 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
> > > --
> > > SEED=94195001484901963602666886307845237936
> > > alias sagetest=".sage -t --long --random-seed=$SEED"
> > > sagetest src/sage/features/interfaces.py # Timed out
> > > sagetest src/sage/game_theory/parser.py # 2 doctests failed
> > > --
> > >
> > > I'll try again with Sage 9.5.rc3 and in case all tests pass
> > > a patchbot on pascaline can be launched again. --Samuel

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/1bb0ad7a-1f29-4a5d-8c8c-9bc87588588dn%40googlegroups.com.

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

[Frédéric Chapoton]

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
> --
> SEED=94195001484901963602666886307845237936
> alias sagetest=".sage -t --long --random-seed=$SEED"
> sagetest src/sage/features/interfaces.py  # Timed out
> sagetest src/sage/game_theory/parser.py  # 2 doctests failed
> --
>
> I'll try again with Sage 9.5.rc3 and in case all tests pass
> a patchbot on pascaline can be launched again.  --Samuel
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/5bb345e3-a77a-4561-a480-a3da9e767809n%40googlegroups.com.

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

[Frédéric Chapoton]

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 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 a écrit :
>
>> 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 emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8995caff-be49-41d2-8396-1337fb5ea569n%40googlegroups.com.

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

[Frédéric Chapoton]

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 a écrit :

> 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 emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d859496c-21e0-4403-a6c3-2edb30af8c37n%40googlegroups.com.

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

[Frédéric Chapoton]

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 emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/2496bd4d-2624-42ed-a99d-b2162b47e6a2n%40googlegroups.com.

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

[Frédéric Chapoton]

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:  
> https://groups.google.com/g/sage-devel/c/jTlgRgLaZuM.
>
> On Thursday, December 16, 2021 at 12:43:44 PM UTC-8 Marcus A. wrote:
>
>> Hi,
>> I tried to build sage 9.4 from source on Ubuntu 21.10.
>> The package cysignals failed to build (see also the attached log files):
>>
>> ...
>> Error building Sage.
>>
>> The following package(s) may have failed to build (not necessarily
>> during this run of 'make all-start'):
>>
>> * package: cysignals-1.10.3
>>   last build time: Dez 16 21:07
>>   log file:/home/marcus/sage-9.4/logs/pkgs/cysignals-1.10.3.log
>>   build directory: 
>> /home/marcus/sage-9.4/local/var/tmp/sage/build/cysignals-1.10.3
>>
>> It is safe to delete any log files and build directories, but they
>> contain information that is helpful for debugging build problems.
>> WARNING: If you now run 'make' again, the build directory of the
>> same version of the package will, by default, be deleted. Set the
>> environment variable SAGE_KEEP_BUILT_SPKGS=yes to prevent this.
>>
>> make[1]: *** [Makefile:39: all-start] Error 1
>> make[1]: Leaving directory '/home/marcus/sage-9.4'
>> make: *** [Makefile:13: all] Error 2
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0e657df9-4a30-46e2-8e08-ddbfeffdeee4n%40googlegroups.com.

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

[Frédéric Chapoton]

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.rings.integer.Integer._shift_helper
Failed example:
try:
print('Possible error output from gmp')
1 << (2^60)
except (MemoryError, OverflowError, RuntimeError):
pass
else:
print("Failed to raise exception")
Expected:
Possible error output from gmp...
Got:
gmp: overflow in mpz type
Possible error output from gmp

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/941f1631-056b-451b-9f28-5e49c79d8155n%40googlegroups.com.

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

[Frédéric Chapoton]

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 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 client owners upgrade to pachtbot 3.0.2
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e20bd760-f1ba-49e5-992a-3a3ddd4258b5n%40googlegroups.com.

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

[Frédéric Chapoton]

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: Pending 
> ok (report successfully posted)   
> [2021-08-14 11:28:38] Done reporting #0 
> base 
> Current base: git://github.com/sagemath/sage.git develop 
> Failing tests in your base install: exiting.
>
> However, ./sage -tp 8 --all --long reports no failure.
>
> The only error message I can find is
>
> Traceback (most recent call last): 
>  File 
> "/home/martin/.local/lib/python3.8/site-packages/sage_patchbot/patchbot.py", 
> line 1150, in test_a_ticket 
>with open(path) as f: 
> FileNotFoundError: [Errno 2] No such file or directory: 
> '/home/martin/sage-patchbot/src/ext/doctest/python3-known-passing.txt' 
> 2021-08-14 11:28:35
>
> What might I be doing wrong?
>
> Martin
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d9ba6b50-6427-4c08-b898-12ec18014b14n%40googlegroups.com.

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

[Frédéric Chapoton]

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)   
> [2021-08-14 11:28:38] Done reporting #0 
> base 
> Current base: git://github.com/sagemath/sage.git develop 
> Failing tests in your base install: exiting.
>
> However, ./sage -tp 8 --all --long reports no failure.
>
> The only error message I can find is
>
> Traceback (most recent call last): 
>  File 
> "/home/martin/.local/lib/python3.8/site-packages/sage_patchbot/patchbot.py", 
> line 1150, in test_a_ticket 
>with open(path) as f: 
> FileNotFoundError: [Errno 2] No such file or directory: 
> '/home/martin/sage-patchbot/src/ext/doctest/python3-known-passing.txt' 
> 2021-08-14 11:28:35
>
> What might I be doing wrong?
>
> Martin
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/28689738-6fdf-4048-b1eb-1784219d34a9n%40googlegroups.com.

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

[Frédéric Chapoton]

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 Michael Orlitzky wrote:
>
>> There's a lot of low-hanging fruit to be had. If you start with 
>> Harald's logo from 
>>
>> https://github.com/sagemath/artwork 
>>
>> and delete all of the noise, for example, you get something 
>> respectable. 
>>
>
> I don't like the font or shape of the logo, which is a play with 
> characters for sci-fi connotation. As a word, the logo is not read smoothly 
> with my eyes. Since I am not native to English, I thought this feeling is 
> just mine. 
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/1fe72ab9-db82-4bb0-b09a-c45c7e49cea8n%40googlegroups.com.

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

[Frédéric Chapoton]

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

>
> Hi,
>
> I'm new to Sage, and I'm running across some unexpected behavior involving 
> numerical evaluation of exponentials involving pi.
>
> In my version (Sagemath 9.2), the following code
> exp(-12.0*pi).n()
> gives the output below.
> 0.000
>
> The true value of the exponential is something like 4e-17: very small, but 
> definitely not zero.  The problem seems to be that Sage internally converts 
> the exponential to a difference (cosh-sinh) of two huge numbers, and then 
> precision problems kick in.
>
> This problem has been brought up before...
> https://ask.sagemath.org/question/57182/numerical-
> approximation-error-involving-cosh-and-sinh/
> ... but the folks over there seem to have concluded (for reasons I don't 
> understand) that the behavior is not a bug at all.
>
> Brian Lawrence
>
> 'SageMath version 9.2, Release Date: 2020-10-24'
>
> (P.S. I ran across this trying to do some computations with q-expansions 
> of modular forms, where these sorts of exponentials are quite common.)
>
> (P.P.S. Apologies if I'm posting this in the wrong place, I'm new here and 
> not familiar with local norms...)
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/bfc7f7d7-57fc-496a-ac42-31fa2f6a2349n%40googlegroups.com.

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

[Frédéric Chapoton]

Hello,

I have now fixed a few svg issues, that were preventing the correct display 
of text in firefox. It was working in chrome.

Nils, would you be so kind as to tell more precisely what you find so 
*atrocious* ? Colors ? shapes ? text ? everything ? any suggestions for 
improvements ?

also, if some users of other browsers could please tell if the logos now 
display correctly ?

Frédéric

Le dimanche 4 juillet 2021 à 19:27:07 UTC+2, Nils Bruin a écrit :

> Oh my, those logos are absolutely atrocious! Never mind the translation: 
> the text is clipped to incomprehensibility anyway (at least when displayed 
> in firefox) -- and that includes the english language one. On the plus 
> side, these logos are so obviously bad that I don't think anybody 
> reasonable will consider using them.
>
> Concerning the dutch translation: Especially for professional/business 
> terminology, the Netherlands have a strong preference for just borrowing 
> the english term (this may be a bit different in Flemish-Belgium), so "open 
> source mathematics" or "open source wiskunde" sounds completely acceptable 
> to me. The most direct translation "vrije broncode wiskunde" sounds a 
> little strange. It would need to be "wiskundige software met open broncode" 
> which doesn't really have a punch. Using "bronnen" (sources) has no 
> software association in dutch at all, so it would seem that it's about 
> mathematics that uses available (historical?) sources rather than secret 
> ones.
>
> As anecdotal evidence of use of english terms in official dutch 
> communication meant for a dutch audience:
>
> https://www.rivm.nl/bevolkingsonderzoeken-en-screeningen/bevolkingsonderzoek-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 at 07:35:11 UTC-7 Frédéric Chapoton wrote:
>
>> So should I replace "wiskunde met vrije licentie" by "open bronnen 
>> wiskunde" ? 
>>
>> This would be a more accurate translation, maybe ?
>>
>> Le vendredi 2 juillet 2021 à 15:43:12 UTC+2, dim...@gmail.com a écrit :
>>
>>> I think one does not translate "open source" 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.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,
>>>> 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 from it, send 
>>>> an email to sage-devel+...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/sage-devel/54fdb0b8-b6a2-4e3a-b052-ab9f861fed0bn%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/sage-devel/54fdb0b8-b6a2-4e3a-b052-ab9f861fed0bn%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/c84245df-f2ef-44d0-af4e-1b6a53842e66n%40googlegroups.com.

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

[Frédéric Chapoton]

So should I replace "wiskunde met vrije licentie" by "open bronnen 
wiskunde" ? 

This would be a more accurate translation, maybe ?

Le vendredi 2 juillet 2021 à 15:43:12 UTC+2, dim...@gmail.com a écrit :

> I think one does not translate "open source" 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.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,
>> 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 from it, send an 
>> email to sage-devel+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/54fdb0b8-b6a2-4e3a-b052-ab9f861fed0bn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/sage-devel/54fdb0b8-b6a2-4e3a-b052-ab9f861fed0bn%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/c850a649-aab9-4e0b-890a-0a8ef9cab98an%40googlegroups.com.

[sage-devel] spoken languages and banner translations

[Frédéric Chapoton]

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,
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 from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/54fdb0b8-b6a2-4e3a-b052-ab9f861fed0bn%40googlegroups.com.

Re: [sage-devel] .configure stalls

[Frédéric Chapoton]

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  
> wrote:
> >
> > I did it again (see below) and it allowed the compilation of sage to 
> start.
> >
> > ~/sage$ sage -pip install --upgrade --force-reinstall numpy
> > Collecting numpy
> > Downloading 
> numpy-1.20.3-cp38-cp38-manylinux_2_12_x86_64.manylinux2010_x86_64.whl (15.4 
> MB)
> > || 15.4 MB 2.9 MB/s
> > Installing collected packages: numpy
> > Attempting uninstall: numpy
> > Found existing installation: numpy 1.20.3
> > Uninstalling numpy-1.20.3:
> > Successfully uninstalled numpy-1.20.3
> > Successfully installed numpy-1.20.3
>
> I don't know how these manylinux2010 wheels are meant to work, but
> here obviously one either had it
> built for the dumbest possible CPU (most probably not the case here)
> or adjust the processor capabilities during the installation,
> something I have no idea how it could work.
>
> Does building sagelib error out just like before?
>
> >
> > Le lundi 21 juin 2021 à 14:35:03 UTC+2, dim...@gmail.com a écrit :
> >>
> >> On the other hand, what did
> >> "sage -pip install numpy" actually do? Did it fetch a binary from the 
> net?
> >> Did it fetch source and built?
> >> On Monday, June 21, 2021 at 1:08:07 PM UTC+1 Dima Pasechnik wrote:
> >>>
> >>> On Mon, Jun 21, 2021 at 10:50 AM Frédéric Chapoton  
> wrote:
> >>> >
> >>> > Hello,
> >>> >
> >>> > So now I am back at the numpy issue when building sagelib, that I 
> sort of "fixed" before by a forced and ugly "sage -pip install numpy".
> >>> >
> >>> > Is my computer just too old ? I add information about it at the end 
> of my message.
> >>> >
> >>> > make --no-print-directory sagelib-SAGE_VENV-no-deps
> >>> > cd '/home/chapoton/sage/build/pkgs/sagelib' && . 
> '/home/chapoton/sage/src/bin/sage-src-env-config' && . 
> '/home/chapoton/sage/src/bin/sage-env-config' && . 
> '/home/chapoton/sage/src/bin/sage-env' && . 
> '/home/chapoton/sage/build/bin/sage-build-env-config' && . 
> '/home/chapoton/sage/build/bin/sage-build-env' && 
> SAGE_SPKG_WHEELS=/home/chapoton/sage/local/var/lib/sage/wheels 
> SAGE_INST_LOCAL=/home/chapoton/sage/local sage-logger -p 
> '/home/chapoton/sage/build/pkgs/sagelib/spkg-install' 
> '/home/chapoton/sage/logs/pkgs/sagelib-9.4.beta2.log'
> >>> > [sagelib-9.4.beta2] Discovering Python/Cython source code
> >>> > [sagelib-9.4.beta2] distributions = ['']
> >>> > [sagelib-9.4.beta2] Discovered Python/Cython sources, time: 19.60 
> seconds.
> >>> > [sagelib-9.4.beta2] running build
> >>> > [sagelib-9.4.beta2] Generating auto-generated sources
> >>> > [sagelib-9.4.beta2] Building interpreters for fast_callable
> >>> > [sagelib-9.4.beta2] -> First build of interpreters
> >>> > [sagelib-9.4.beta2] running build_cython
> >>> > [sagelib-9.4.beta2] Enabling Cython debugging support
> >>> > [sagelib-9.4.beta2] 
> 
> >>> > [sagelib-9.4.beta2] Traceback (most recent call last):
> >>> > [sagelib-9.4.beta2] File "setup.py", line 96, in 
> >>> > [sagelib-9.4.beta2] code = setup(
> >>> > [sagelib-9.4.beta2] File 
> "/home/chapoton/sage/local/lib/python3.8/site-packages/setuptools/__init__.py",
>  
> line 153, in setup
> >>> > [sagelib-9.4.beta2] return distutils.core.setup(**attrs)
> >>> > [sagelib-9.4.beta2] File 
> "/home/chapoton/sage/local/lib/python3.8/site-packages/setuptools/_distutils/core.py",
>  
> line 148, in setup
> >>> > [sagelib-9.4.beta2] dist.run_commands()
> >>> > [sagelib-9.4.beta2] File 
> "/home/chapoton/sage/local/lib/python3.8/site-packages/setuptools/_distutils/dist.py",
>  
> line 967, in run_commands
> >>> > [sagelib-9.4.beta2] self.run_command(cmd)
> >>> > [sagelib-9.4.beta2] File 
> "/home/chapoton/sage/local/lib/python3.8/site-packages/setuptools/_distutils/dist.py",
>  
> line 986, in run_command
> >>> > [sagelib-9.4.beta2] cmd_obj.run()
> >&g

Re: [sage-devel] .configure stalls

[Frédéric Chapoton]

fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr 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 spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs 
itlb_multihit
bogomips : 4788.38

Le lundi 21 juin 2021 à 08:59:28 UTC+2, Frédéric Chapoton a écrit :

> 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 Chapoton  
>> wrote: 
>> > 
>> > 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 .configure is no longer working. 
>> It reaches the following point and then stay there forever : 
>> > 
>> > Checking whether SageMath should install SPKG pari... 
>> > checking whether any of gmp mpir readline is installed as or will be 
>> installed as SPKG... no 
>> > checking for gp... /usr/local/bin/gp 
>> > checking for gphelp... /usr/bin/gphelp 
>>
>> in your PATH you have two different versions of pari installed, one in 
>> /usr, and another in /usr/local 
>>
>> this wreaks havoc. 
>>
>>
>> > checking whether gphelp has access to the documentation... yes 
>> > checking is pari_elldata installed? ... 
>> > 
>> > I am on ubuntu 20.04, and pari-elldata is installed. 
>> > 
>> > I tried in a fresh clone of the sage repo, very same problem. I also 
>> removed my .sage. 
>> > 
>> > 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 from it, send 
>> an email to sage-devel+...@googlegroups.com. 
>> > To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/d199241b-ddc3-4b4d-9f26-1fa67b4941f2n%40googlegroups.com.
>>  
>>
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/763f8650-9803-4bba-a0ec-46744204fc22n%40googlegroups.com.

Re: [sage-devel] .configure stalls

[Frédéric Chapoton]

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 Chapoton  
> wrote:
> >
> > 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 .configure is no longer working. 
> It reaches the following point and then stay there forever :
> >
> > Checking whether SageMath should install SPKG pari...
> > checking whether any of gmp mpir readline is installed as or will be 
> installed as SPKG... no
> > checking for gp... /usr/local/bin/gp
> > checking for gphelp... /usr/bin/gphelp
>
> in your PATH you have two different versions of pari installed, one in
> /usr, and another in /usr/local
>
> this wreaks havoc.
>
>
> > checking whether gphelp has access to the documentation... yes
> > checking is pari_elldata installed? ...
> >
> > I am on ubuntu 20.04, and pari-elldata is installed.
> >
> > I tried in a fresh clone of the sage repo, very same problem. I also 
> removed my .sage.
> >
> > 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 from it, send 
> an email to sage-devel+...@googlegroups.com.
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/d199241b-ddc3-4b4d-9f26-1fa67b4941f2n%40googlegroups.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/cd3325d0-e346-4cbb-a3f6-026b4559194cn%40googlegroups.com.

[sage-devel] .configure stalls

[Frédéric Chapoton]

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 .configure is no longer working. It 
reaches the following point and then stay there forever :

Checking whether SageMath should install SPKG pari...
checking whether any of gmp mpir readline is installed as or will be 
installed as SPKG... no
checking for gp... /usr/local/bin/gp
checking for gphelp... /usr/bin/gphelp
checking whether gphelp has access to the documentation... yes
checking is pari_elldata installed? ...

I am on ubuntu 20.04, and pari-elldata is installed.

I tried in a fresh clone of the sage repo, very same problem. I also 
removed my .sage.

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 from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d199241b-ddc3-4b4d-9f26-1fa67b4941f2n%40googlegroups.com.

[sage-devel] workers for docker images on gitlab

[Frédéric Chapoton]

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 client owners upgrade to pachtbot 3.0.2

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a5d89cb8-209e-42e3-84cf-52f52b9eafefn%40googlegroups.com.

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

[Frédéric Chapoton]

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. Madison Bray  
> wrote:
> >
> > On Thu, Mar 11, 2021 at 12:52 PM Dima Pasechnik  
> wrote:
> > >
> > > On Thu, Mar 11, 2021 at 10:11 AM Dima Pasechnik  
> wrote:
> > > >
> > > > On Wed, Mar 10, 2021 at 4:00 PM E. Madison Bray  
> wrote:
> > > > >
> > > > > On Tue, Jan 12, 2021 at 11:33 PM tobia...@gmx.de  
> wrote:
> > > > > >
> > > > > >
> > > > > > For what's worth, + 1 for migrating to github.
> > > > > >
> > > > > > The interface is cleaner, it has many more features and 
> integrations, and is more active which could attract more contributions. 
> There are a few scripts/tools that allow to migrate from trac to github. 
> But most of them are unmaintained for a few years already, so I'm not sure 
> if they still work (which should be taken as a sign that one should migrate 
> sooner than later).
> > > > >
> > > > > In 2019 Julian Rüth and I, with the help of some others, already 
> put
> > > > > in some effort to set up an organization for SageMath on GitLab:
> > > > > https://gitlab.com/sagemath
> > > > >
> > > > > Between GitHub and GitLab, we felt that the latter would be more
> > > > > acceptable to the broader Sage community. We also implemented a bot
> > > > > that can mirror GitLab merge requests as Trac tickets, though it's
> > > > > been in need of troubleshooting for a while.
> > > > >
> > > > > This was also done before the advent of GitHub Actions, and the
> > > > > ability to provide custom CI runners for GitLab Pipelines seemed
> > > > > advantageous, since we could maintain our own fleet of runners, be 
> it
> > > > > on Sage developers' personal machines (if they are generous enough 
> to
> > > > > host them) or any conceivable constellation of cloud computing
> > > > > platforms.
> > > > >
> > > > > In practice this has gained little traction, in part due to lack of
> > > > > advertising. The GitLab Runner solution also proved a bit 
> troublesome
> > > > > to maintain, as it required some constant attention to make sure 
> there
> > > > > were always working runners available. I tried to keep that up for 
> a
> > > > > while myself, but have had other obligations.
> > > >
> > > > I think it should be mentioned that GitLab has an analog of GitHub 
> Actions,
> > > > and the difference is that its runners may be self-hosted, or 
> provided
> > > > by GitLab.
> > > > E.g. see https://gitlab.com/sagemath/dev/trac/-/pipelines/266731297
> > >
> > > I just tried to switch to a "community" runner, and got an error which
> > > is probably
> > > obvious to people versed in Docker:
> > >
> > > https://gitlab.com/sagemath/dev/trac/-/jobs/1089520433
> >
> > I think it might be because the Docker builds have been otherwise not
> > working for a while (due to lack of reliable runners). So a more
> > recent "build-from-clean" job is needed. These jobs are run when
> > develop/master are updated as well as on tags. Whereas
> > "built-from-latest" is run on branches for tickets. It tries to build
> > the branch on top of the "latest" Docker image e.g. for develop. But
> > the last one that built successfully is too old, and so trying to make
> > the diff between that ticket and the version of develop it's based on
> > fails. Hence the message:
> >
> > "Could not find commit fbca269f627bf6a8bc6f0a611ed7e26260ebc994 in
> > your local Git history. Please merge in the latest built develop
> > branch to fix this: git fetch trac && git merge
> > fbca269f627bf6a8bc6f0a611ed7e26260ebc994"
> >
> > But for the automated CI that's not a very useful message...
> >
> > I know Matthias has done some impressive things to get around GitHub
> > Actions' time limit on jobs by breaking the build up into "stages"
> > that can be split across multiple jobs. I see no reason that couldn't
> > work with GitLab as well.
> >
> > But it would still be better to have our own fleet of runners--they
> > would be faster, and we could test on more different custom hardware
> > configurations. The problem is that this is at a minimum a part-time
> > job...
>
> Well looks like I need to correct the record a bit. Perhaps I've been
> a bit too sanguine about the state of the GitLab builds. In fact, the
> latest develop commit, 9.3beta8, built quite successfully:
> https://gitlab.com/sagemath/sage/-/pipelines/266734885
>
> And it ran on one of the fleet of runners I've been maintaining here
> at Paris-Saclay, which I haven't touched in months. So I guess it's
> still working after all ^^; Ever since I set this up I had been
> having a problem with runners randomly erroring out, and not being
> deleted correctly when they do. I have tried many times to fix it to
> no avail, and I kind of gave up for a while. I assumed eventually
> this caused things 

[sage-devel] patchbot owners, please upgrade

[Frédéric Chapoton]

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 group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/647ade8d-825b-49a0-b9a8-b4ee90192e00n%40googlegroups.com.

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

[Frédéric Chapoton]

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 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 probably change them to use the correct line break
> Le jeudi 11 février 2021 à 10:21:26 UTC+1, john.c...@gmail.com a écrit :
>
>> On Wed, 10 Feb 2021 at 18:07, Dima Pasechnik  wrote: 
>> > 
>> > On Wed, Feb 10, 2021 at 5:49 PM John Cremona  
>> wrote: 
>> > > 
>> > > On Wed, 10 Feb 2021 at 16:56, Dima Pasechnik  
>> wrote: 
>> > > > 
>> > > > On Wed, Feb 10, 2021 at 2:58 PM John Cremona  
>> wrote: 
>> > > > > 
>> > > > > Has anyone else been seeing the following problem, which has been 
>> > > > > plaguing me for a week or two. Here's a simple example. All 
>> > > > > computers mentioned here are running ubuntu. On a machine I had 
>> not 
>> > > > > used for a while I had a sage build of the develop branch at an 
>> old 
>> > > > > version (pre 9.0). There were no modified files (git status 
>> showed 
>> > > > > nothing). Then I did "git pull trac develop", after which one 
>> file is 
>> > > > > marked as having changed: 
>> > > > > 
>> > > > > modified: src/sage/misc/element_with_label.py 
>> > > > > 
>> > > > > It is always this file, on several machines where I have gone 
>> through 
>> > > > > similar steps. file shows this: 
>> > > > > src/sage/misc/element_with_label.py: Python script, ASCII text 
>> > > > > executable, with CRLF line terminators 
>> > > > 
>> > > > does 
>> > > > 
>> > > > git config core.autolf 
>> > > > 
>> > > > show 'true'? 
>> > > 
>> > > No. 
>> > > 
>> > > > 
>> > > > Set it to false, IMHO this should fix this issue. 
>> > > 
>> > > It is not set at all. I saw that option after googling for help, but 
>> > > the issue it exists to solve is not one which has ever hit me (in 
>> sage 
>> > > anyway, of course I know about using dos2unix sometimes when a 
>> windows 
>> > > users sends a file). 
>> > 
>> > did you try setting this option to false, and see if it helps? 
>>
>> Not yet systematically. After setting it to false and doing nothing 
>> else, git status still shows 
>> src/sage/misc/element_with_label.py as modified, even after 'git 
>> checkout --'. Trying to get back to sanity a different way, 'git 
>> stash' now outputs 
>>
>>
>> warning: CRLF will be replaced by LF in 
>> src/sage/misc/element_with_label.py. 
>> The file will have its original line endings in your working directory. 
>> warning: CRLF will be replaced by LF in 
>> src/sage/misc/element_with_label.py. 
>> The file will have its original line endings in your working directory. 
>> Saved working directory and index state WIP on develop: 8453ffb 
>> Updated SageMath version to 9.3.beta7 
>> HEAD is now at 8453ffb Updated SageMath version to 9.3.beta7 
>>
>> but git status still shows that file as modified. Now I cannot just 
>> checkout a different existing branch (since there are apparently 
>> modified files), but I can checkout a new branch (g = alias for git) 
>>
>> $ g co -b dud 
>> M src/sage/misc/element_with_label.py 
>> Switched to a new branch 'dud' 
>>
>> the delete the 'develop' branch (which was the same as upstream anyway): 
>>
>> $ g branch -d develop 
>> Deleted branch develop (was 8453ffb). 
>>
>> and now recreate the develop branch 
>>
>> $ g remote update trac 
>> (...) 
>> $ g co -b develop trac/develop 
>> M src/sage/misc/element_with_label.py 
>> Branch develop set up to track remote branch develop from trac. 
>> Switched to a new branch 'develop' 
>>
>> and we are back to where we started. All of the above was with 
>> core.autolf set to false. 
>>
>> On the same machine, in a completely new clone made and built 
>> yesterday, git status shows 
>>
>

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

[Frédéric Chapoton]

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 probably change them to use the correct line break
Le jeudi 11 février 2021 à 10:21:26 UTC+1, john.c...@gmail.com a écrit :

> On Wed, 10 Feb 2021 at 18:07, Dima Pasechnik  wrote: 
> > 
> > On Wed, Feb 10, 2021 at 5:49 PM John Cremona  
> wrote: 
> > > 
> > > On Wed, 10 Feb 2021 at 16:56, Dima Pasechnik  
> wrote: 
> > > > 
> > > > On Wed, Feb 10, 2021 at 2:58 PM John Cremona  
> wrote: 
> > > > > 
> > > > > Has anyone else been seeing the following problem, which has been 
> > > > > plaguing me for a week or two. Here's a simple example. All 
> > > > > computers mentioned here are running ubuntu. On a machine I had 
> not 
> > > > > used for a while I had a sage build of the develop branch at an 
> old 
> > > > > version (pre 9.0). There were no modified files (git status showed 
> > > > > nothing). Then I did "git pull trac develop", after which one file 
> is 
> > > > > marked as having changed: 
> > > > > 
> > > > > modified: src/sage/misc/element_with_label.py 
> > > > > 
> > > > > It is always this file, on several machines where I have gone 
> through 
> > > > > similar steps. file shows this: 
> > > > > src/sage/misc/element_with_label.py: Python script, ASCII text 
> > > > > executable, with CRLF line terminators 
> > > > 
> > > > does 
> > > > 
> > > > git config core.autolf 
> > > > 
> > > > show 'true'? 
> > > 
> > > No. 
> > > 
> > > > 
> > > > Set it to false, IMHO this should fix this issue. 
> > > 
> > > It is not set at all. I saw that option after googling for help, but 
> > > the issue it exists to solve is not one which has ever hit me (in sage 
> > > anyway, of course I know about using dos2unix sometimes when a windows 
> > > users sends a file). 
> > 
> > did you try setting this option to false, and see if it helps? 
>
> Not yet systematically. After setting it to false and doing nothing 
> else, git status still shows 
> src/sage/misc/element_with_label.py as modified, even after 'git 
> checkout --'. Trying to get back to sanity a different way, 'git 
> stash' now outputs 
>
>
> warning: CRLF will be replaced by LF in 
> src/sage/misc/element_with_label.py. 
> The file will have its original line endings in your working directory. 
> warning: CRLF will be replaced by LF in 
> src/sage/misc/element_with_label.py. 
> The file will have its original line endings in your working directory. 
> Saved working directory and index state WIP on develop: 8453ffb 
> Updated SageMath version to 9.3.beta7 
> HEAD is now at 8453ffb Updated SageMath version to 9.3.beta7 
>
> but git status still shows that file as modified. Now I cannot just 
> checkout a different existing branch (since there are apparently 
> modified files), but I can checkout a new branch (g = alias for git) 
>
> $ g co -b dud 
> M src/sage/misc/element_with_label.py 
> Switched to a new branch 'dud' 
>
> the delete the 'develop' branch (which was the same as upstream anyway): 
>
> $ g branch -d develop 
> Deleted branch develop (was 8453ffb). 
>
> and now recreate the develop branch 
>
> $ g remote update trac 
> (...) 
> $ g co -b develop trac/develop 
> M src/sage/misc/element_with_label.py 
> Branch develop set up to track remote branch develop from trac. 
> Switched to a new branch 'develop' 
>
> and we are back to where we started. All of the above was with 
> core.autolf set to false. 
>
> On the same machine, in a completely new clone made and built 
> yesterday, git status shows 
>
> $ g st 
> On branch develop 
> Your branch is up-to-date with 'origin/develop'. 
> Changes not staged for commit: 
> (use "git add ..." to update what will be committed) 
> (use "git checkout -- ..." to discard changes in working directory) 
>
> modified: src/sage/rings/invariants/__init__.py 
>
> no changes added to commit (use "git add" and/or "git commit -a") 
>
> So the same problem with a new file -- which only has 2 bytes in it! 
> AFter dos2unix-ing it (so it now has 1 byte) it is still showing up in 
> git status. AFter git checkout -- it goes back to having 2 bytes and 
> still shows up. 
>
> It seems to be impossible to do any sage development here. I am now 
> trying yet another git clone -- so the global config of core.autolf is 
> in force as the clone is made -- but then after the clone from 
> git://github.com/sagemath/sage.git that same file is shown as 
> modified. For some reason I have been making the cones from github 
> and then adding trac as a remote. As a variant I made a fresh clone 
> from trac -- but see exactly the same. 
>
> A similar problem was reported on stackexchange *over 9 years ago* by 
> a Mac users whose collaborators were all ubuntu users. There, it is 
> suggest to look at the .gitattributes file, and 

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

[Frédéric Chapoton]

did you run

docker run -it sagemath/sagemath-dev:develop

or something else ?

Le lundi 28 décembre 2020 à 12:45:20 UTC+1, seb@gmail.com a écrit :

> It seems that there is still (or again) something broken. For the images 
> of the beta releases since the 8th of December Sage crashes if I try to 
> start it:
>
> Sage build/upgrade complete!
> make[1]: Leaving directory '/home/sage/sage'
> sage@8711c66abafe:~/sage$ ./sage
> ┌┐
> │ SageMath version 9.3.beta5, Release Date: 2020-12-27   │
> │ Using Python 3.8.5. Type "help()" for help.│
> └┘
> ┏┓
> ┃ Warning: this is a prerelease version, and it may be unstable. ┃
> ┗┛
> 
> /home/sage/sage/local/lib/python3.8/site-packages/cysignals/signals.cpython-38-x86_64-linux-gnu.so(+0x6b28)[0x7ff042b33b28]
> /home/sage/sage/local/lib/python3.8/site-packages/cysignals/signals.cpython-38-x86_64-linux-gnu.so(+0x6d08)[0x7ff042b33d08]
> /home/sage/sage/local/lib/python3.8/site-packages/cysignals/signals.cpython-38-x86_64-linux-gnu.so(+0x93a0)[0x7ff042b363a0]
> /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7ff0523f9390]
> /home/sage/sage/local/lib/libgmp.so.10(__gmpz_sizeinbase+0x47)[0x7ff049df0597]
> /home/sage/sage/local/lib/python3.8/site-packages/sage/rings/rational.cpython-38-x86_64-linux-gnu.so(+0x1f78c)[0x7ff036e2978c]
> /home/sage/sage/local/lib/python3.8/site-packages/sage/rings/rational.cpython-38-x86_64-linux-gnu.so(+0x370d5)[0x7ff036e410d5]
> 
> /home/sage/sage/local/lib/libpython3.8.so.1.0(+0x185260)[0x7ff05278a260]
> /home/sage/sage/local/lib/libpython3.8.so.1.0(PyRun_FileExFlags+0x95)[0x7ff05278cb45]
> /home/sage/sage/local/lib/libpython3.8.so.1.0(PyRun_SimpleFileExFlags+0xf6)[0x7ff05278ccb6]
> /home/sage/sage/local/lib/libpython3.8.so.1.0(Py_RunMain+0x748)[0x7ff0527a7398]
> /home/sage/sage/local/lib/libpython3.8.so.1.0(Py_BytesMain+0x39)[0x7ff0527a77c9]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7ff05203e840]
> python3(_start+0x29)[0x400709]
> 
> Attaching gdb to process id 9075.
> Cannot find gdb installed
> GDB is not installed.
> Install gdb for enhanced tracebacks.
> 
> Unhandled SIGILL: An illegal instruction occurred.
> This probably occurred because a *compiled* module has a bug
> in it and is not properly wrapped with sig_on(), sig_off().
> Python will now terminate.
> ----
> 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 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 Vincent, I learned recently how to use continuous integration 
>>> in gitlab and the docker images of previous versions of sage posted 
>>> https://hub.docker.com/r/sagemath/sagemath-dev/ in order to test that 
>>> my optional package works with all those versions. It basically made me 
>>> realize that my package was broken on most versions of sage except the most 
>>> recent. And hopefully soon, I will be able to fix those issues. So thanks 
>>> to those involved in having these various docker images available.
>>>
>>> For the curious, the most recent run is available here:
>>> https://gitlab.com/seblabbe/slabbe/-/pipelines/202932270
>>> it shows that my package works for 9.1.rc5 but not 9.0 or earlier 
>>> versions (I need to work on it).
>>>
>>> Unfortunately, it seems the docker images of various versions of sage 
>>> are not uploaded since 4 months. Maybe it was too much energy to upload all 
>>> beta versions there. In fact, I don't really need all beta in there. What I 
>>> think is important to have are the final releases. With that respect, the 
>>> following are missing:
>>>
>>> 8.6: ok
>>> 8.7: ok
>>> 8.8: ok
>>> 8.9

[sage-devel] Re: Weird power series bug

[Frédéric Chapoton]

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 series when computing the inverse of a 
> serie. Look at this.
>
> This computation gives the expected result
>
> sage: L. = LazyPowerSeriesRing(QQ) 
>   
> sage: f = 1 - z - z^2 
>   
> sage: b = ~f   
>  
> sage: b.compute_coefficients(10)   
>  
> sage: b   
>   
> 1 + z + 2*z^2 + 3*z^3 + 5*z^4 + 8*z^5 + 13*z^6 + 21*z^7 + 34*z^8 + 55*z^9 
> + 89*z^10 + O(x^11)
>
> But not this one:
>
> sage: L. = LazyPowerSeriesRing(QQ) 
>   
> sage: f = 1 - z - z^2 
>   
> sage: f.compute_coefficients(10)   
>  
> sage: f   
>   
> 1 - z - z^2 + O(x^11)
> sage: b = ~f   
>  
> sage: b.compute_coefficients(10)   
>  
> sage: b   
>   
> 1 + z^1 + z^2 + z^3 + ...
>
> Another example with Catalan numbers
>
> sage: L. = LazyPowerSeriesRing(QQ)  
> sage: C = L() 
>   
> sage: C.define(1 + z*C*C) 
>   
> sage: Cinv = ~C   
>   
> sage: Cinv.compute_coefficients(10); Cinv 
>   
> 1 - z - z^2 - 2*z^3 - 5*z^4 - 14*z^5 - 42*z^6 - 132*z^7 - 429*z^8 - 
> 1430*z^9 - 4862*z^10 + O(x^11)
>
> sage: C = L() 
>   
> sage: C.define(1 +z*C*C)   
>  
> sage: C.compute_coefficients(10);C 
>  
> 1 + z + 2*z^2 + 5*z^3 + 14*z^4 + 42*z^5 + 132*z^6 + 429*z^7 + 1430*z^8 + 
> 4862*z^9 + 16796*z^10 + O(x^11)
> sage: Cinv = ~C   
>   
> sage: Cinv.compute_coefficients(10);Cinv   
>  
> 1 + z^1 + z^2 + z^3 + ...
>
> How Come?? 
>
> This is Sage 9.2. I haven't tried on other versions
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f4ab89bb-0a1f-482f-a841-aa61e66507bcn%40googlegroups.com.

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

[Frédéric Chapoton]

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 Vincent, I learned recently how to use continuous integration in 
> gitlab and the docker images of previous versions of sage posted 
> https://hub.docker.com/r/sagemath/sagemath-dev/ in order to test that my 
> optional package works with all those versions. It basically made me 
> realize that my package was broken on most versions of sage except the most 
> recent. And hopefully soon, I will be able to fix those issues. So thanks 
> to those involved in having these various docker images available.
>
> For the curious, the most recent run is available here:
> https://gitlab.com/seblabbe/slabbe/-/pipelines/202932270
> it shows that my package works for 9.1.rc5 but not 9.0 or earlier versions 
> (I need to work on it).
>
> Unfortunately, it seems the docker images of various versions of sage are 
> not uploaded since 4 months. Maybe it was too much energy to upload all 
> beta versions there. In fact, I don't really need all beta in there. What I 
> think is important to have are the final releases. With that respect, the 
> following are missing:
>
> 8.6: ok
> 8.7: ok
> 8.8: ok
> 8.9 is missing or is broken
> 9.0 : ok
> 9.1 is missing (so I am using 9.1.rc5 and 9.1.rc5-py3)
>
> No 9.2.betaX are there, but I would be happy that 9.2 be there when 
> released.
>
> Thanks to the people involved.
>
> Sincerely,
>
> Sébastien
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8196c783-fbfd-475f-8a29-2b7b13da6325n%40googlegroups.com.

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

[Frédéric Chapoton]

Hello Erik,
So, one year later, can you please put a branch somewhere on trac ?
Frédéric
Le lundi 2 décembre 2019 à 12:50:44 UTC+1, erik@gmail.com a écrit :

> Thanks, I forgot about this. IIRC it was still a little buggy, but I
> can see if I can resurrect what I did have and make a 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
> >
> > 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
> >> even with parallel docbuilds.
> >>
> >> I think there are still some bugs and other kinks to work out so it
> >> will take a little more time to get this really polished up, but what
> >> do you think? Would anyone else like to have this? Is it worth
> >> spending any more time on?
> >
> > --
> > You received this message because you are subscribed to the Google 
> Groups "sage-devel" group.
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to sage-devel+...@googlegroups.com.
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/2ac5a8d1-29c2-4ed0-bd06-b6a06b590b83%40googlegroups.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/51945ce3-26b9-4e4a-b65c-a6237c9f240an%40googlegroups.com.

[sage-devel] Re: Docker images

[Frédéric Chapoton]

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 \{\} \;
>  find: ‘src/build’: No such file or directory
>  Makefile:151: recipe for target 'fast-rebuild-clean' failed
>  make: *** [fast-rebuild-clean] Error 1
>  
> Le dimanche 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+1, Marc Mezzarobba a écrit :
>>
>>> Dima Pasechnik wrote: 
>>> > hopefully everything needed to fix docker builds will be merged in the 
>>> > coming beta. 
>>>
>>> Ok, thank you! 
>>>
>>> -- 
>>> Marc 
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/97729989-772c-42b2-9532-c976ddc72827n%40googlegroups.com.

[sage-devel] Re: Docker images

[Frédéric Chapoton]

now the docker building process on gitlab fails here, for the latest 
develop 9.3.beta2 :

 find src/build -name '*.py' -exec rm \{\} \;
 find: ‘src/build’: No such file or directory
 Makefile:151: recipe for target 'fast-rebuild-clean' failed
 make: *** [fast-rebuild-clean] Error 1
 
Le dimanche 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+1, Marc Mezzarobba a écrit :
>
>> Dima Pasechnik wrote: 
>> > hopefully everything needed to fix docker builds will be merged in the 
>> > coming beta. 
>>
>> Ok, thank you! 
>>
>> -- 
>> Marc 
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/eec532e7-58b6-4d34-91fd-d39b6caec534n%40googlegroups.com.

Re: [sage-devel] patchbots meet segmentation fault

[Frédéric Chapoton]

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) ?
> if you can reproduce this locally, perhaps you can try increasing 0.5
> and see if it makes a difference.
>
> > One should probably open a ticket..
> right.
> >
> > Le dimanche 22 novembre 2020 à 09:58:29 UTC+1, dim...@gmail.com a écrit 
> :
> >>
> >> the test (I saw this test failing before) in question is some kind of 
> hack:
> >>
> >> sage: try:
> >> alarm(0.5)
> >> singular._expect_expr('>') # interrupt this
> >> except KeyboardInterrupt:
> >> pass ## line 505 ##
> >> Control-C pressed. Interrupting Singular. Please wait a few seconds...
> >> sage: 2*a ## line 514 ##
> >> 
> >> /home/chapoton/sage/local/lib/python3.8/site-packages/cysignals/
> signals.cpython-38-x86_64-linux-gnu.so(+0x7df4)[0x7f7c33af8df4]
> >> 
> >>
> >> perhaps a kind of race condition - I don't want to think what happens
> >> if Control-C does not propagate quickly enough to suspend
> >> 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 for singular, namely:
> >> >
> >> > sage -t --long --random-seed=0 src/sage/interfaces/singular.py # 
> Killed due to segmentation fault
> >> >
> >> > The tested file also fails when run alone, but the copy-pasted test 
> works fine.
> >> >
> >> > Frédéric
> >> >
> >> > PS : for full logs, see
> >> >
> >> > 
> https://patchbot.sagemath.org/log/0/Darwin/Darwin%20Kernel%20Version%2018.5.0:%20Mon%20Mar%2011%2020:40:32%20PDT%202019;%20root:xnu-4903.251.3~3/RELEASE_X86_64/x86_64/18.5.0/steenrod/2020-11-07%2019:50:32?short
> >> >
> >> > 
> https://patchbot.sagemath.org/log/0/Linux/57-Ubuntu_SMP_Thu_Oct_15_10:57:00_UTC_2020/x86_64/5.4.0-52-generic/petitbonum/2020-11-07%2020:48:10?short
> >> >
> >> > --
> >> > You received this message because you are subscribed to the Google 
> Groups "sage-devel" group.
> >> > To unsubscribe from this group and stop receiving emails from it, 
> send an email to sage-devel+...@googlegroups.com.
> >> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/54c8dd1f-5efa-4a9f-b17f-4225ef9c6c91n%40googlegroups.com
> .
> >
> > --
> > You received this message because you are subscribed to the Google 
> Groups "sage-devel" group.
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to sage-devel+...@googlegroups.com.
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/6d949ff6-3fac-4436-be17-9e466f19424bn%40googlegroups.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/cb0a540b-ccb9-4e58-9e9d-84849cf55731n%40googlegroups.com.

Re: [sage-devel] patchbots meet segmentation fault

[Frédéric Chapoton]

Thanks. I agree. So what to do ? Remove the doctest ? Change the alarm(0.5) 
? One should probably open a ticket..

Le dimanche 22 novembre 2020 à 09:58:29 UTC+1, dim...@gmail.com a écrit :

> the test (I saw this test failing before) in question is some kind of hack:
>
> sage: try:
> alarm(0.5)
> singular._expect_expr('>') # interrupt this
> except KeyboardInterrupt:
> pass ## line 505 ##
> Control-C pressed. Interrupting Singular. Please wait a few seconds...
> sage: 2*a ## line 514 ##
> 
> /home/chapoton/sage/local/lib/python3.8/site-packages/cysignals/
> signals.cpython-38-x86_64-linux-gnu.so(+0x7df4)[0x7f7c33af8df4]
> 
>
> perhaps a kind of race condition - I don't want to think what happens
> if Control-C does not propagate quickly enough to suspend
> 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 for singular, namely:
> >
> > sage -t --long --random-seed=0 src/sage/interfaces/singular.py # Killed 
> due to segmentation fault
> >
> > The tested file also fails when run alone, but the copy-pasted test 
> works fine.
> >
> > Frédéric
> >
> > PS : for full logs, see
> >
> > 
> https://patchbot.sagemath.org/log/0/Darwin/Darwin%20Kernel%20Version%2018.5.0:%20Mon%20Mar%2011%2020:40:32%20PDT%202019;%20root:xnu-4903.251.3~3/RELEASE_X86_64/x86_64/18.5.0/steenrod/2020-11-07%2019:50:32?short
> >
> > 
> https://patchbot.sagemath.org/log/0/Linux/57-Ubuntu_SMP_Thu_Oct_15_10:57:00_UTC_2020/x86_64/5.4.0-52-generic/petitbonum/2020-11-07%2020:48:10?short
> >
> > --
> > You received this message because you are subscribed to the Google 
> Groups "sage-devel" group.
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to sage-devel+...@googlegroups.com.
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/54c8dd1f-5efa-4a9f-b17f-4225ef9c6c91n%40googlegroups.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/6d949ff6-3fac-4436-be17-9e466f19424bn%40googlegroups.com.

[sage-devel] patchbots meet segmentation fault

[Frédéric Chapoton]

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 fails when run alone, but the copy-pasted test works 
fine.

Frédéric

PS : for full logs, see

https://patchbot.sagemath.org/log/0/Darwin/Darwin%20Kernel%20Version%2018.5.0:%20Mon%20Mar%2011%2020:40:32%20PDT%202019;%20root:xnu-4903.251.3~3/RELEASE_X86_64/x86_64/18.5.0/steenrod/2020-11-07%2019:50:32?short

https://patchbot.sagemath.org/log/0/Linux/57-Ubuntu_SMP_Thu_Oct_15_10:57:00_UTC_2020/x86_64/5.4.0-52-generic/petitbonum/2020-11-07%2020:48:10?short

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/54c8dd1f-5efa-4a9f-b17f-4225ef9c6c91n%40googlegroups.com.

[sage-devel] Re: Docker images

[Frédéric Chapoton]

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 docker builds will be merged in the
> > coming beta.
>
> Ok, thank you!
>
> -- 
> Marc
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/30a1b219-cc84-48da-b69b-6e9c9da74e08n%40googlegroups.com.

[sage-devel] cocalc and sagemath webpage

[Frédéric Chapoton]

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 website, should we just 
accept this without any kind of discussion ?

Maybe cocalc could become one of our sponsors, as a display of explicit and 
permanent friendship ?

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 from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/91cd2053-daeb-40b5-986e-20ae547ff181n%40googlegroups.com.

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

[Frédéric Chapoton]

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 
>
> 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 :
>
>> artifact complains about our patches not applying:
>>
>> [planarity-3.0.0.5.p0] patching file c/planarity.h
>> [planarity-3.0.0.5.p0] Hunk #1 FAILED at 77 (different line endings).
>> [planarity-3.0.0.5.p0] Hunk #2 FAILED at 88 (different line endings).
>> [planarity-3.0.0.5.p0] 2 out of 2 hunks FAILED -- 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"
>>>
>>> see 
>>> https://gitlab.com/sagemath/dev/trac/-/pipelines/213154052
>>> Le jeudi 5 novembre 2020 à 11:06:28 UTC+1, Sébastien Labbé a écrit :
>>>
>>>> At
>>>> https://hub.docker.com/r/sagemath/sagemath-dev/tags
>>>> tags are 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://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 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 adapted to use python3 by default. And 
>>>>>>> there is a complaint about
>>>>>>>
>>>>>>> .ci/build-docker.sh: line 60: syntax error: unterminated quoted 
>>>>>>> string
>>>>>>>
>>>>>>> but the script looks ok to me.
>>>>>>>
>>>>>>> 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ébastien Labbé a écrit :
>>>>>>>>
>>>>>>>>> Bonjour,
>>>>>>>>>
>>>>>>>>> Thanks to Vincent, I learned recently how to use continuous 
>>>>>>>>> integration in gitlab and the docker images of previous versions of 
>>>>>>>>> sage 
>>>>>>>>> posted https://hub.docker.com/r/sagemath/sagemath-dev/ in order 
>>>>>>>>> to test that my optional package works with all those versions. It 
>>>>>>>>> basically made me realize that my package was broken on most versions 
>>>>>>>>> of 
>>>>>>>>> sage except the most recent. And hopefully soon, I will be able to 
>>>>>>>>> fix 
>>>>>>>>> those issues. So thanks to those involved in having these various 
>>>>>>>>> docker 
>>>>>>>>> images available.
>>>>>>>>>
>>>>>>>>> For the curious, the most recent run is available here:
>>>>>>>>> https://gitlab.com/seblabbe/slabbe/-/pipelines/202932270
>>>>>>>>> it shows that my package works for 9.1.rc5 but not 9.0 or earlier 
>>>>>>>>> versions (I need to work on it).
>>>>>>>>>
>>>>>>>>> Unfortunately, it seems the docker images of various versions of 
>>>>>>>>> sage are not uploaded since 4 months. Maybe it was too much energy to 
>>>>>>>>> upload all beta versions there. In fact, I don't really need all beta 
>>>>>>>>> in 
>>>>>>>>> there. What I think is important to have are the final releases. With 
>>>>>>>>> that 
>>>>>>>>> respect, the following are missing:
>>>>>>>>>
>>>>>>>>> 8.6: ok
>>>>>>>>> 8.7: ok
>>>>>>>>> 8.8: ok
>>>>>>>>> 8.9 is missing or is broken
>>>>>>>>> 9.0 : ok
>>>>>>>>> 9.1 is missing (so I am using 9.1.rc5 and 9.1.rc5-py3)
>>>>>>>>>
>>>>>>>>> No 9.2.betaX are there, but I would be happy that 9.2 be there 
>>>>>>>>> when released.
>>>>>>>>>
>>>>>>>>> Thanks to the people involved.
>>>>>>>>>
>>>>>>>>> Sincerely,
>>>>>>>>>
>>>>>>>>> Sébastien
>>>>>>>>>
>>>>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/9818282b-b1df-4fab-b771-eda47748e5ddn%40googlegroups.com.

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

[Frédéric Chapoton]

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 :

> artifact complains about our patches not applying:
>
> [planarity-3.0.0.5.p0] patching file c/planarity.h
> [planarity-3.0.0.5.p0] Hunk #1 FAILED at 77 (different line endings).
> [planarity-3.0.0.5.p0] Hunk #2 FAILED at 88 (different line endings).
> [planarity-3.0.0.5.p0] 2 out of 2 hunks FAILED -- 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"
>>
>> see 
>> https://gitlab.com/sagemath/dev/trac/-/pipelines/213154052
>> Le jeudi 5 novembre 2020 à 11:06:28 UTC+1, Sébastien Labbé a écrit :
>>
>>> At
>>> https://hub.docker.com/r/sagemath/sagemath-dev/tags
>>> tags are 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://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 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 adapted to use python3 by default. And 
>>>>>> there is a complaint about
>>>>>>
>>>>>> .ci/build-docker.sh: line 60: syntax error: unterminated quoted string
>>>>>>
>>>>>> but the script looks ok to me.
>>>>>>
>>>>>> 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ébastien Labbé a écrit :
>>>>>>>
>>>>>>>> Bonjour,
>>>>>>>>
>>>>>>>> Thanks to Vincent, I learned recently how to use continuous 
>>>>>>>> integration in gitlab and the docker images of previous versions of 
>>>>>>>> sage 
>>>>>>>> posted https://hub.docker.com/r/sagemath/sagemath-dev/ in order to 
>>>>>>>> test that my optional package works with all those versions. It 
>>>>>>>> basically 
>>>>>>>> made me realize that my package was broken on most versions of sage 
>>>>>>>> except 
>>>>>>>> the most recent. And hopefully soon, I will be able to fix those 
>>>>>>>> issues. So 
>>>>>>>> thanks to those involved in having these various docker images 
>>>>>>>> available.
>>>>>>>>
>>>>>>>> For the curious, the most recent run is available here:
>>>>>>>> https://gitlab.com/seblabbe/slabbe/-/pipelines/202932270
>>>>>>>> it shows that my package works for 9.1.rc5 but not 9.0 or earlier 
>>>>>>>> versions (I need to work on it).
>>>>>>>>
>>>>>>>> Unfortunately, it seems the docker images of various versions of 
>>>>>>>> sage are not uploaded since 4 months. Maybe it was too much energy to 
>>>>>>>> upload all beta versions there. In fact, I don't really need all beta 
>>>>>>>> in 
>>>>>>>> there. What I think is important to have are the final releases. With 
>>>>>>>> that 
>>>>>>>> respect, the following are missing:
>>>>>>>>
>>>>>>>> 8.6: ok
>>>>>>>> 8.7: ok
>>>>>>>> 8.8: ok
>>>>>>>> 8.9 is missing or is broken
>>>>>>>> 9.0 : ok
>>>>>>>> 9.1 is missing (so I am using 9.1.rc5 and 9.1.rc5-py3)
>>>>>>>>
>>>>>>>> No 9.2.betaX are there, but I would be happy that 9.2 be there when 
>>>>>>>> released.
>>>>>>>>
>>>>>>>> Thanks to the people involved.
>>>>>>>>
>>>>>>>> Sincerely,
>>>>>>>>
>>>>>>>> Sébastien
>>>>>>>>
>>>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/2ba48906-aa94-40b8-ad70-f54e9a540086n%40googlegroups.com.

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

[Frédéric Chapoton]

artifact complains about our patches not applying:

[planarity-3.0.0.5.p0] patching file c/planarity.h
[planarity-3.0.0.5.p0] Hunk #1 FAILED at 77 (different line endings).
[planarity-3.0.0.5.p0] Hunk #2 FAILED at 88 (different line endings).
[planarity-3.0.0.5.p0] 2 out of 2 hunks FAILED -- 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"
>
> see 
> https://gitlab.com/sagemath/dev/trac/-/pipelines/213154052
> Le jeudi 5 novembre 2020 à 11:06:28 UTC+1, Sébastien Labbé a écrit :
>
>> At
>> https://hub.docker.com/r/sagemath/sagemath-dev/tags
>> tags are 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://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 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 adapted to use python3 by default. And 
>>>>> there is a complaint about
>>>>>
>>>>> .ci/build-docker.sh: line 60: syntax error: unterminated quoted string
>>>>>
>>>>> but the script looks ok to me.
>>>>>
>>>>> 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ébastien Labbé a écrit :
>>>>>>
>>>>>>> Bonjour,
>>>>>>>
>>>>>>> Thanks to Vincent, I learned recently how to use continuous 
>>>>>>> integration in gitlab and the docker images of previous versions of 
>>>>>>> sage 
>>>>>>> posted https://hub.docker.com/r/sagemath/sagemath-dev/ in order to 
>>>>>>> test that my optional package works with all those versions. It 
>>>>>>> basically 
>>>>>>> made me realize that my package was broken on most versions of sage 
>>>>>>> except 
>>>>>>> the most recent. And hopefully soon, I will be able to fix those 
>>>>>>> issues. So 
>>>>>>> thanks to those involved in having these various docker images 
>>>>>>> available.
>>>>>>>
>>>>>>> For the curious, the most recent run is available here:
>>>>>>> https://gitlab.com/seblabbe/slabbe/-/pipelines/202932270
>>>>>>> it shows that my package works for 9.1.rc5 but not 9.0 or earlier 
>>>>>>> versions (I need to work on it).
>>>>>>>
>>>>>>> Unfortunately, it seems the docker images of various versions of 
>>>>>>> sage are not uploaded since 4 months. Maybe it was too much energy to 
>>>>>>> upload all beta versions there. In fact, I don't really need all beta 
>>>>>>> in 
>>>>>>> there. What I think is important to have are the final releases. With 
>>>>>>> that 
>>>>>>> respect, the following are missing:
>>>>>>>
>>>>>>> 8.6: ok
>>>>>>> 8.7: ok
>>>>>>> 8.8: ok
>>>>>>> 8.9 is missing or is broken
>>>>>>> 9.0 : ok
>>>>>>> 9.1 is missing (so I am using 9.1.rc5 and 9.1.rc5-py3)
>>>>>>>
>>>>>>> No 9.2.betaX are there, but I would be happy that 9.2 be there when 
>>>>>>> released.
>>>>>>>
>>>>>>> Thanks to the people involved.
>>>>>>>
>>>>>>> Sincerely,
>>>>>>>
>>>>>>> Sébastien
>>>>>>>
>>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/aa0dba89-4a84-4af8-b9b8-5778eb8e07ddn%40googlegroups.com.

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

[Frédéric Chapoton]

The 9.3.beta1 build on gitlab is blocked by a failure with "planarity"

see 
https://gitlab.com/sagemath/dev/trac/-/pipelines/213154052
Le jeudi 5 novembre 2020 à 11:06:28 UTC+1, Sébastien Labbé a écrit :

> At
> https://hub.docker.com/r/sagemath/sagemath-dev/tags
> tags are 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://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 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 adapted to use python3 by default. And 
>>>> there is a complaint about
>>>>
>>>> .ci/build-docker.sh: line 60: syntax error: unterminated quoted string
>>>>
>>>> but the script looks ok to me.
>>>>
>>>> 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ébastien Labbé a écrit :
>>>>>
>>>>>> Bonjour,
>>>>>>
>>>>>> Thanks to Vincent, I learned recently how to use continuous 
>>>>>> integration in gitlab and the docker images of previous versions of sage 
>>>>>> posted https://hub.docker.com/r/sagemath/sagemath-dev/ in order to 
>>>>>> test that my optional package works with all those versions. It 
>>>>>> basically 
>>>>>> made me realize that my package was broken on most versions of sage 
>>>>>> except 
>>>>>> the most recent. And hopefully soon, I will be able to fix those issues. 
>>>>>> So 
>>>>>> thanks to those involved in having these various docker images available.
>>>>>>
>>>>>> For the curious, the most recent run is available here:
>>>>>> https://gitlab.com/seblabbe/slabbe/-/pipelines/202932270
>>>>>> it shows that my package works for 9.1.rc5 but not 9.0 or earlier 
>>>>>> versions (I need to work on it).
>>>>>>
>>>>>> Unfortunately, it seems the docker images of various versions of sage 
>>>>>> are not uploaded since 4 months. Maybe it was too much energy to upload 
>>>>>> all 
>>>>>> beta versions there. In fact, I don't really need all beta in there. 
>>>>>> What I 
>>>>>> think is important to have are the final releases. With that respect, 
>>>>>> the 
>>>>>> following are missing:
>>>>>>
>>>>>> 8.6: ok
>>>>>> 8.7: ok
>>>>>> 8.8: ok
>>>>>> 8.9 is missing or is broken
>>>>>> 9.0 : ok
>>>>>> 9.1 is missing (so I am using 9.1.rc5 and 9.1.rc5-py3)
>>>>>>
>>>>>> No 9.2.betaX are there, but I would be happy that 9.2 be there when 
>>>>>> released.
>>>>>>
>>>>>> Thanks to the people involved.
>>>>>>
>>>>>> Sincerely,
>>>>>>
>>>>>> Sébastien
>>>>>>
>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/46266088-0d5a-4bd1-99bb-0882adab27e4n%40googlegroups.com.

[sage-devel] help for testing #30765 ?

[Frédéric Chapoton]

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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/7a938c46-6c74-469b-9174-b78f2a97e5f4n%40googlegroups.com.

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

[Frédéric Chapoton]

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 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 adapted to use python3 by default. And there 
>> is a complaint about
>>
>> .ci/build-docker.sh: line 60: syntax error: unterminated quoted string
>>
>> but the script looks ok to me.
>>
>> 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ébastien Labbé a écrit :
>>>
>>>> Bonjour,
>>>>
>>>> Thanks to Vincent, I learned recently how to use continuous integration 
>>>> in gitlab and the docker images of previous versions of sage posted 
>>>> https://hub.docker.com/r/sagemath/sagemath-dev/ in order to test that 
>>>> my optional package works with all those versions. It basically made me 
>>>> realize that my package was broken on most versions of sage except the 
>>>> most 
>>>> recent. And hopefully soon, I will be able to fix those issues. So thanks 
>>>> to those involved in having these various docker images available.
>>>>
>>>> For the curious, the most recent run is available here:
>>>> https://gitlab.com/seblabbe/slabbe/-/pipelines/202932270
>>>> it shows that my package works for 9.1.rc5 but not 9.0 or earlier 
>>>> versions (I need to work on it).
>>>>
>>>> Unfortunately, it seems the docker images of various versions of sage 
>>>> are not uploaded since 4 months. Maybe it was too much energy to upload 
>>>> all 
>>>> beta versions there. In fact, I don't really need all beta in there. What 
>>>> I 
>>>> think is important to have are the final releases. With that respect, the 
>>>> following are missing:
>>>>
>>>> 8.6: ok
>>>> 8.7: ok
>>>> 8.8: ok
>>>> 8.9 is missing or is broken
>>>> 9.0 : ok
>>>> 9.1 is missing (so I am using 9.1.rc5 and 9.1.rc5-py3)
>>>>
>>>> No 9.2.betaX are there, but I would be happy that 9.2 be there when 
>>>> released.
>>>>
>>>> Thanks to the people involved.
>>>>
>>>> Sincerely,
>>>>
>>>> Sébastien
>>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/06a7dabb-6ce3-4764-84af-2dde25d184e7n%40googlegroups.com.

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

[Frédéric Chapoton]

Build failure comes from not being able to pull something :

+ docker pull source-clean
Error response from daemon: pull access denied for source-clean, repository 
does not exist or may require 'docker login': denied: requested access to 
the resource is denied



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ébastien Labbé a écrit :
>
>> Bonjour,
>>
>> Thanks to Vincent, I learned recently how to use continuous integration 
>> in gitlab and the docker images of previous versions of sage posted 
>> https://hub.docker.com/r/sagemath/sagemath-dev/ in order to test that my 
>> optional package works with all those versions. It basically made me 
>> realize that my package was broken on most versions of sage except the most 
>> recent. And hopefully soon, I will be able to fix those issues. So thanks 
>> to those involved in having these various docker images available.
>>
>> For the curious, the most recent run is available here:
>> https://gitlab.com/seblabbe/slabbe/-/pipelines/202932270
>> it shows that my package works for 9.1.rc5 but not 9.0 or earlier 
>> versions (I need to work on it).
>>
>> Unfortunately, it seems the docker images of various versions of sage are 
>> not uploaded since 4 months. Maybe it was too much energy to upload all 
>> beta versions there. In fact, I don't really need all beta in there. What I 
>> think is important to have are the final releases. With that respect, the 
>> following are missing:
>>
>> 8.6: ok
>> 8.7: ok
>> 8.8: ok
>> 8.9 is missing or is broken
>> 9.0 : ok
>> 9.1 is missing (so I am using 9.1.rc5 and 9.1.rc5-py3)
>>
>> No 9.2.betaX are there, but I would be happy that 9.2 be there when 
>> released.
>>
>> Thanks to the people involved.
>>
>> Sincerely,
>>
>> Sébastien
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/5ca854a0-c02a-43a9-a843-384efc5d3820n%40googlegroups.com.

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

[Frédéric Chapoton]

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 adapted to use python3 by default. And there 
> is a complaint about
>
> .ci/build-docker.sh: line 60: syntax error: unterminated quoted string
>
> but the script looks ok to me.
>
> 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ébastien Labbé a écrit :
>>
>>> Bonjour,
>>>
>>> Thanks to Vincent, I learned recently how to use continuous integration 
>>> in gitlab and the docker images of previous versions of sage posted 
>>> https://hub.docker.com/r/sagemath/sagemath-dev/ in order to test that 
>>> my optional package works with all those versions. It basically made me 
>>> realize that my package was broken on most versions of sage except the most 
>>> recent. And hopefully soon, I will be able to fix those issues. So thanks 
>>> to those involved in having these various docker images available.
>>>
>>> For the curious, the most recent run is available here:
>>> https://gitlab.com/seblabbe/slabbe/-/pipelines/202932270
>>> it shows that my package works for 9.1.rc5 but not 9.0 or earlier 
>>> versions (I need to work on it).
>>>
>>> Unfortunately, it seems the docker images of various versions of sage 
>>> are not uploaded since 4 months. Maybe it was too much energy to upload all 
>>> beta versions there. In fact, I don't really need all beta in there. What I 
>>> think is important to have are the final releases. With that respect, the 
>>> following are missing:
>>>
>>> 8.6: ok
>>> 8.7: ok
>>> 8.8: ok
>>> 8.9 is missing or is broken
>>> 9.0 : ok
>>> 9.1 is missing (so I am using 9.1.rc5 and 9.1.rc5-py3)
>>>
>>> No 9.2.betaX are there, but I would be happy that 9.2 be there when 
>>> released.
>>>
>>> Thanks to the people involved.
>>>
>>> Sincerely,
>>>
>>> Sébastien
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/5d83939b-f695-4a31-b0c4-2a4ec5455c2cn%40googlegroups.com.

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

[Frédéric Chapoton]

I can see recent tentatives from Orsay, but they failed. Maybe Erik did 
launch a runner there ?

Our .ci setting needs to be adapted to use python3 by default. And there is 
a complaint about

.ci/build-docker.sh: line 60: syntax error: unterminated quoted string

but the script looks ok to me.

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ébastien Labbé a écrit :
>
>> Bonjour,
>>
>> Thanks to Vincent, I learned recently how to use continuous integration 
>> in gitlab and the docker images of previous versions of sage posted 
>> https://hub.docker.com/r/sagemath/sagemath-dev/ in order to test that my 
>> optional package works with all those versions. It basically made me 
>> realize that my package was broken on most versions of sage except the most 
>> recent. And hopefully soon, I will be able to fix those issues. So thanks 
>> to those involved in having these various docker images available.
>>
>> For the curious, the most recent run is available here:
>> https://gitlab.com/seblabbe/slabbe/-/pipelines/202932270
>> it shows that my package works for 9.1.rc5 but not 9.0 or earlier 
>> versions (I need to work on it).
>>
>> Unfortunately, it seems the docker images of various versions of sage are 
>> not uploaded since 4 months. Maybe it was too much energy to upload all 
>> beta versions there. In fact, I don't really need all beta in there. What I 
>> think is important to have are the final releases. With that respect, the 
>> following are missing:
>>
>> 8.6: ok
>> 8.7: ok
>> 8.8: ok
>> 8.9 is missing or is broken
>> 9.0 : ok
>> 9.1 is missing (so I am using 9.1.rc5 and 9.1.rc5-py3)
>>
>> No 9.2.betaX are there, but I would be happy that 9.2 be there when 
>> released.
>>
>> Thanks to the people involved.
>>
>> Sincerely,
>>
>> Sébastien
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/261c7a7b-9c88-4cea-a4ad-7bae888a3b7en%40googlegroups.com.

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

[Frédéric Chapoton]

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 in 
> gitlab and the docker images of previous versions of sage posted 
> https://hub.docker.com/r/sagemath/sagemath-dev/ in order to test that my 
> optional package works with all those versions. It basically made me 
> realize that my package was broken on most versions of sage except the most 
> recent. And hopefully soon, I will be able to fix those issues. So thanks 
> to those involved in having these various docker images available.
>
> For the curious, the most recent run is available here:
> https://gitlab.com/seblabbe/slabbe/-/pipelines/202932270
> it shows that my package works for 9.1.rc5 but not 9.0 or earlier versions 
> (I need to work on it).
>
> Unfortunately, it seems the docker images of various versions of sage are 
> not uploaded since 4 months. Maybe it was too much energy to upload all 
> beta versions there. In fact, I don't really need all beta in there. What I 
> think is important to have are the final releases. With that respect, the 
> following are missing:
>
> 8.6: ok
> 8.7: ok
> 8.8: ok
> 8.9 is missing or is broken
> 9.0 : ok
> 9.1 is missing (so I am using 9.1.rc5 and 9.1.rc5-py3)
>
> No 9.2.betaX are there, but I would be happy that 9.2 be there when 
> released.
>
> Thanks to the people involved.
>
> Sincerely,
>
> Sébastien
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/26665361-9abb-4e7e-a136-c49e0574b676n%40googlegroups.com.

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

[Frédéric Chapoton]

-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 RealField and/or RR.  I see the 
> need for a "genuine real field", but it seems a lot simpler just to call it 
> something other than "RealField" and so not break a lot of existing users' 
> Sage code.
>
> Best,
>
> Nathan
>
> On Wednesday, October 14, 2020 at 1:28:08 AM UTC-5 vdelecroix wrote:
>
>> Dear all,
>>
>> I would like to discuss the patchbomb at
>>
>> https://trac.sagemath.org/ticket/24523
>>
>> The ticket hopes to change the string representation from
>> "Real Field with XX bits of precision" to "Real Floating-point
>> field with XX bits of precision".
>>
>> Rationale: it was quite unfortunate from the beginning that
>> RealField and ComplexField mean "floating-point arithmetic".
>> On the one hand, one would like to be able to work with the
>> (abstract) Parent modeling the real numbers (eg for coercions).
>> On the other hand, in the setting of computer algebra it is
>> very often much better to work with interval arithmetic or
>> balls rather than floating-point. The ticket is a small
>> step towards getting the genuine "RealField" standing for
>> the set of real numbers. See
>>
>> https://trac.sagemath.org/ticket/17713
>>
>> I think this deserves an agreement from other developers! Any
>> comment very welcome.
>>
>> Best
>> Vincent
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d9e2e654-6cb8-42b7-821f-2be818332451n%40googlegroups.com.

[sage-devel] sage -i fricas broken ?

[Frédéric Chapoton]

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] 

[fricas-1.3.6] 

[fricas-1.3.6] Error downloading fricas-1.3.6-full.tar.bz2

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a249e97f-8734-437d-abef-2244928e6a22n%40googlegroups.com.

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

[Frédéric Chapoton]

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*), Integer(*1*
> ))]]).cardinality()
>
> 2
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f20b29b7-3aa9-4401-98fd-9205f7353f48o%40googlegroups.com.

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

[Frédéric Chapoton]

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 the FTP protocol:
>
> ftp://ftp.fu-berlin.de/unix/misc/sage/index.html
>
> This page can be viewed in Firefox, but not in Chromium or Google Chrome, 
> due to the following:
>
> Rendering FTP resources (removed)
> https://www.chromestatus.com/feature/619900567552
>
> What happens instead is that the HTML file is downloaded. This is very 
> confusing for new users.
> (Particularly for my students [in Germany], who will be visiting the 
> downloads page later this month.)
>
> One may disagree with the behavior of Chromium/Chrome, but it is a fact 
> that they have a large user base.
> So I propose removing ftp:// links from the main downloads page(s), 
> preferably soon.
> If not removing, then I would at least add a warning next to the link.
> Of course it is preferable to replace the link with a more accessible one 
> eventually.
>
> Best regards,
> Ricardo
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/71825fd1-b91f-4cc5-8a6d-c644fe6cd2e4%40googlegroups.com.

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

[Frédéric Chapoton]

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 suggested in the .c file, it 
gives me Segmentation faults :

sage: pari('idtowd([2,3])')
---
SignalError   Traceback (most recent call last)
 in ()
> 1 pari('idtowd([2,3])')


cypari2/pari_instance.pyx in cypari2.pari_instance.Pari.__call__()


cypari2/gen.pyx in cypari2.gen.objtogen()


cypari2/convert.pyx in cypari2.convert.PyObject_AsGEN()


SignalError: Segmentation fault

What am I doing wrong ? What is the proper way to use compiled gp scripts 
from sage ?

Cheers, and take care.

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 from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/488b1bb3-3e6d-44e9-bae5-e7302f084cb9%40googlegroups.com.

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

[Frédéric Chapoton]

> 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 to returning the domain. I want to 
> get to the definition of _cache_an_element() function. However, I have been 
> unable to find this even using silver searcher on the entire repository. 
> I'm sorry if this is a very stupid question. Can someone please explain to 
> me where this function is defined as it is present in almost all the 
> classes.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8d90a7e3-85cb-4efe-b88a-1b823b5f46a7%40googlegroups.com.

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

[Frédéric Chapoton]

This has been a long discussion already. Let me try to summarize. My 
question was :

  *Do you agree that sage release 9.1 (and most of the 9.1.betas) will not 
be kept compatible with Python 2 ?*

Some people give a more or less clear *positive* answer :

Chapoton, Bissey, Gourgoulhon, Kaufmann, Novoseltsev, Koeppe, Mantysalo, 
Rojas, Isuru, Stein, Dunfield, Pasechnik (*12*)

Some people give a strong *negative* answer :

Bruin, Bray (*2*)

Some people did not answer the question in a clear way, but still said 
*something* :

Palmieri, Roe, King, Crisman, Delecroix, Scrimshaw, Kliem, Labbé, Braun (*9*
)

Among them, I would say that maybe 5 people were rather negative on the 
question.

I hope that I have not forgotten anybody or misinterpreted wildly.

[A] It seems to me that the conclusion of the vote is rather clear, and 
that we should not feel obliged to make 9.1 compilable with python2.

==> I have therefore changed the controversial wiki page, to make only the 
statement that 9.0 is compilable with python2. No more promise for the 
future.

[B] I understand and approve the concerns about our user base. We should 
really try harder to listen more and help people that are simple users.

So here is my proposal.

* Starting from now, we allow ourselves to move on, using 9.1 betas and 
further releases for external python3 updates, including switch to 
ipython7, which seems to me the most urgent matter. But we also do not 
introduce python3-only code in our own code base if we can avoid it.

* Concerning semantic versioning, I would advocate to use 10.0 as the first 
release where all compatibility code will be removed, hence pure py3. This 
may take some time, given the sparse work force. Once done, we allow 
ourself to use python3-only syntax in our own codebase, such as "yield 
from".

Therefore, we can use 9.1, 9.2 and so on until somebody™ does the job of 
cleaning up sagemath codebase from remains of py2-only code.

I have tried to make a balanced and reasonable proposal. Applause or scream 
at your will.

Frederic






Le dimanche 5 janvier 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 if we 
> insist on maintaining a codebase that is both compatible with python 2 and 
> python 3.
>
> So, please vote :
>
>
>
> 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 from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/9db91206-3a7c-434a-8b07-7656e5b5f458%40googlegroups.com.

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

[Frédéric Chapoton]

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 a Dell Inspiron 13, 5000 series, running
> Ubuntu Linux 18.01.
>
> The error in building R as seen in the attached log
> led to the overall build failing. I would have liked
> to have an updated sage having just changed Linux
> distro to Ubuntu. Advice on how to fix this welcomed!
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/ac7a9100-4255-4dc0-993d-9221fd39ace4%40googlegroups.com.

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

[Frédéric Chapoton]

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 immediate drop of python2, and for 
removing the promise that 9.1 will be py2-compatible

F

Le dimanche 5 janvier 2020 22:06:21 UTC+1, Nils Bruin a écrit :
>
> I think our wiki vetoes that idea. See 
> https://wiki.sagemath.org/Python3-Switch :
>
> Compiling with Python 2 
>
> After version 9.0, if you really want so, you can still build and use 
> SageMath with *Python 2*, as follows. 
>
> make configure./configure --with-python=2make build
>
> Beware that you will need to call the second line again if you ever call 
> "make distclean". 
> This will work until version 9.1 at least. Then the backward compatibility 
> with Python 2 will no longer be ensured. 
>
> If you want to drop py2 compatibility very soon, the only option is to 
> release 9.1 basically right now, identical to 9.0, and then get on with 
> developing 9.2. That's a nasty thing to do. Based on previous release 
> schedules, people would be justified in expecting that <=9.1 is the 
> "current" release until at least June 2020 or so. So we're stuck with py2 
> compatibility until that time.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/11341de1-238b-4abe-b617-e328af87b639%40googlegroups.com.

[sage-devel] drop python2 compatibility in 9.1 ?

[Frédéric Chapoton]

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 
python 3.

So, please vote :

Do you agree that sage release 9.1 (and most of the 9.1.betas) will not be 
kept compatible with Python 2 ?

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 from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/692fc332-d9e6-4e6a-80fe-2e89cf0b488f%40googlegroups.com.

[sage-devel] Re: Problems setting patchbots

[Frédéric Chapoton]

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 to 
>> investigate. Maybe the # in the patchbot name is not a good idea (random 
>> guess) ?
>>
>>
> It looks like that could be the culprit, since It also happens in other 
> machines. Any idea on how it could be solved? 
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/6b1597c1-a993-4e3a-ba39-627230a1b294%40googlegroups.com.

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

[Frédéric Chapoton]

The patchbot named "sage4" has been banned from posting its reports. It 
will be unbanned when Jeroen tells us that he is taking care.

F

Le vendredi 6 décembre 2019 10:04:34 UTC+1, Dima Pasechnik a écrit :
>
> As Jeroen, who runs that bot, appears to be AWOL, this bot has 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 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 noticed that the following patchbot reports systematic builds errors 
>>> (after only 10s) 
>>>
>>> Gentoo Base System/2.2/x86_64/4.14.78-gentoo/sage4 
>>> <https://patchbot.sagemath.org/ticket/?machine=GentooBaseSystem=2.2=x86_64=4.14.78-gentoo=sage4=open>
>>>
>>> Shouln't this bot be banned since it produces massive amount of falty 
>>> reports?
>>>
>>>
>>> See :
>>> https://patchbot.sagemath.org/ticket/?machine=Gentoo%20Base%20System=2.2=x86_64=4.14.78-gentoo=sage4=open
>>>
>>>
>>>
>>>
>>> Léo Brunswic
>>>
>> -- 
>> 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-...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/51c31c15-bf8b-421e-bc50-8b52986698b6%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/sage-devel/51c31c15-bf8b-421e-bc50-8b52986698b6%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/32d8c6e0-ac54-4573-8e5f-44ff04383ed7%40googlegroups.com.

[sage-devel] Re: Problems setting patchbots

[Frédéric Chapoton]

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 :
>
> I am setting up several virtual machines with different distros to run 
> patchbots on them. In particular I want to use different distros (including 
> less usual ones) to get more diversity in the patchbot set.
>
> However, I am finding some problems:
>
> A debian machine is returning the following error when testing the base 
> install:
>
> sage -t --long --warn-long 41.0 src/sage/tests/gap_packages.py
> **
> File "src/sage/tests/gap_packages.py", line 8, in sage.tests.gap_packages
> Failed example:
> test_packages(pkgs, only_failures=True)# optional - gap_packages
> Expected:
>   Status   Package   GAP Output
> ++-++
> Got:
> #I  method installed for Matrix matches more than one declaration
>   Status   Package   GAP Output
> ++-++
> **
> 1 item had failures:
>1 of   5 in sage.tests.gap_packages
> [11 tests, 1 failure, 3.59 s]
> --
> sage -t --long --warn-long 41.0 src/sage/tests/gap_packages.py  # 1 
> doctest failed
> --
> Total time for all tests: 4752.5 seconds
> cpu time: 7926.2 seconds
> cumulative wall time: 9116.0 seconds
>
>
> In particular, it is this machine:
>
>
> https://patchbot.sagemath.org/ticket/?machine=debian=10.2=x86_64=4.19.0-6-amd64=localhost=open
>
>
> Another one, running OpenSUSE, is also givin the same error, but besides, 
> doesn't seem to be sending reports to the server:
>
>
> https://patchbot.sagemath.org/log/0/Linux/#1%20SMP%20Wed%20Nov%2013%2007:50:15%20UTC%202019%20(6e1aaad)/x86_64/4.12.14-lp151.28.32-default/pb-unizar-opensuse/2019-12-06%2011:48:21
>
>
>
>
> Any clues?
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/298b4329-6384-4ed7-a930-d6fc9cf04656%40googlegroups.com.

[sage-devel] Re: mad patchbot?

[Frédéric Chapoton]

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 noticed that the following patchbot reports systematic builds errors 
> (after only 10s) 
>
> Gentoo Base System/2.2/x86_64/4.14.78-gentoo/sage4 
> 
>
> Shouln't this bot be banned since it produces massive amount of falty 
> reports?
>
>
> See :
> https://patchbot.sagemath.org/ticket/?machine=Gentoo%20Base%20System=2.2=x86_64=4.14.78-gentoo=sage4=open
>
>
>
>
> Léo Brunswic
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/51c31c15-bf8b-421e-bc50-8b52986698b6%40googlegroups.com.

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

[Frédéric Chapoton]

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 
> even with parallel docbuilds. 
>
> I think there are still some bugs and other kinks to work out so it 
> will take a little more time to get this really polished up, but what 
> do you think?  Would anyone else like to have this?  Is it worth 
> spending any more time on? 
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/2ac5a8d1-29c2-4ed0-bd06-b6a06b590b83%40googlegroups.com.

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

[Frédéric Chapoton]

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 2019 15:13:50 UTC+1, Jori Mäntysalo (TAU) a écrit :
>
> I did a fresh install, i.e. start from git clone 
> git://github.com/sagemath/sage.git and so on. Sage starts and I can start 
> jupyter also. However ./sage --notebook=sagenb says 
>
> DeprecationWarning: the imp module is deprecated in favour of importlib; 
> see the module's documentation for alternative uses 
>import imp 
> Traceback (most recent call last): 
>   . . . 
>  from twisted.mail import smtp, relaymanager  # problematic with 
> python 3 
> ImportError: cannot import name 'smtp' from 'twisted.mail' (unknown 
> location) 
>
> So have we broken sagenb totally when moving to Python 3? 
>
> -- 
> Jori Mäntysalo 
>
> Tampereen yliopisto - Ihminen ratkaisee

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/879b6b57-8c37-456c-bb96-25b610ea1c7a%40googlegroups.com.

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

[Frédéric Chapoton]

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 patchbot on python2, which could be useful, 
you will need to do once

make configure
./configure --with-python=2
make

and hopefully the patchbot will remain using python2 after each release.

Frederic


-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/6efa7518-3a3d-44c7-9964-d86cb93ab672%40googlegroups.com.

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

[Frédéric Chapoton]

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 that. I think now would 
> be a good time to flip the switch, though. Any thoughts?
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/ad9edbd6-525f-4e6c-8036-3d962e6d07a1%40googlegroups.com.

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

[Frédéric Chapoton]

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, though. Any thoughts?
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/93184645-b6ee-431b-bf8a-51344c32e537%40googlegroups.com.

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

[Frédéric Chapoton]

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 excuse).  
> However, in truth the problem is slightly deeper.
>
> The superficial problem at hand is that unicode_art produces garbled 
> output on my emacs (I am running GNU Emacs 24.5.1, which is admittedly old).
>
> I am not sure how I can best describe the problem, so I attached a 
> screenshot: of the output of 
>
> sage: unicode_art(SkewPartitions(3).list())
>
> The deeper problem is, that sage-shell-mode (which is mostly wonderful), 
> is not really maintained anymore.  The git repository is 
> https://github.com/sagemath/sage-shell-mode.
>
> For example, there is a pull request with a one-line fix by Frederic 
> Chapoton (thank you!), which is sitting there since a month.
>
> Are there any emacs experts out there?  Should sage-shell-mode become a 
> part of sagemath, to make maintainance easier?
>
> Martin
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/7c87189a-9752-4f84-a9c7-2acc1b35a365%40googlegroups.com.

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

[Frédéric Chapoton]

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 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 the number sqrt(2) as a cyclotomic or as a real 
>> number. Please look at the example:
>>
>> sage: K.=CyclotomicField(8)
>> sage: a=z-z^3  # a is a square root of 2
>> sage: a-sqrt(2)
>> 0
>> sage: 
>> Q=QuadraticForm(K,8,[1/2,-a/2,0,0,0,0,0,0,1/2,-a/2,0,0,0,0,0,1/2,-1/2,0,0,
>> : 0,0,1/2,-1/2,0,0,0,1/2,-1/2,0,0,1/2,-a/2,0,1/2,-a/2,1/2])
>> sage: Q.signature_vector()
>> (8, 0, 0)
>>
>> this cannot be true since there exists an isotropic vector:
>>
>> sage: v=vector([1,a,1,0,0,0,0,0])
>> sage: v*Q.matrix()*v
>> 0
>>
>> Let's try it over reals:
>>
>> sage: a=sqrt(2)
>> sage: 
>> Q=QuadraticForm(RR,8,[1/2,-a/2,0,0,0,0,0,0,1/2,-a/2,0,0,0,0,0,1/2,-1/2,0,0
>> : ,0,0,1/2,-1/2,0,0,0,1/2,-1/2,0,0,1/2,-a/2,0,1/2,-a/2,1/2])
>> sage: Q.signature_vector()
>> (6, 2, 0)
>>
>> however, the isotropic vector above is not isotropic anymore:
>>
>> sage: v=vector([1,a,1,0,0,0,0,0])
>> sage: v*Q.matrix()*v
>> sqrt(2)*(1.00*sqrt(2) - 1.41421356237310) - 
>> 1.41421356237310*sqrt(2) + 2.00
>>
>> I also tried to define 
>>
>> sage: a=sqrt(AA(2))
>> sage: 
>> Q=QuadraticForm(AA,8,[1/2,-a/2,0,0,0,0,0,0,1/2,-a/2,0,0,0,0,0,1/2,-1/2,0,0
>> : ,0,0,1/2,-1/2,0,0,0,1/2,-1/2,0,0,1/2,-a/2,0,1/2,-a/2,1/2])
>>
>> but Q.signature_vector() gives a runtime error with many lines of code 
>> ending in:
>>
>> RuntimeError: maximum recursion depth exceeded
>>
>>
>> Questions:
>> 1) is Q.signature_vector() over cyclotomic field is interpreted in some 
>> other way than for reals, thus making the result (8,0,0) somehow correct?
>>
>> 2) Which setting would guarantee both the correct result for 
>> signature_vector() using the exact arithmetic and at the same time show 
>> that v is actually an isotropic vector?
>>
>> Thank you!
>>
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/710cf4ab-c782-4ad0-a195-fcd47ed1abc5%40googlegroups.com.

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

[Frédéric Chapoton]

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 the number sqrt(2) as a cyclotomic or as a real 
> number. Please look at the example:
>
> sage: K.=CyclotomicField(8)
> sage: a=z-z^3  # a is a square root of 2
> sage: a-sqrt(2)
> 0
> sage: 
> Q=QuadraticForm(K,8,[1/2,-a/2,0,0,0,0,0,0,1/2,-a/2,0,0,0,0,0,1/2,-1/2,0,0,
> : 0,0,1/2,-1/2,0,0,0,1/2,-1/2,0,0,1/2,-a/2,0,1/2,-a/2,1/2])
> sage: Q.signature_vector()
> (8, 0, 0)
>
> this cannot be true since there exists an isotropic vector:
>
> sage: v=vector([1,a,1,0,0,0,0,0])
> sage: v*Q.matrix()*v
> 0
>
> Let's try it over reals:
>
> sage: a=sqrt(2)
> sage: 
> Q=QuadraticForm(RR,8,[1/2,-a/2,0,0,0,0,0,0,1/2,-a/2,0,0,0,0,0,1/2,-1/2,0,0
> : ,0,0,1/2,-1/2,0,0,0,1/2,-1/2,0,0,1/2,-a/2,0,1/2,-a/2,1/2])
> sage: Q.signature_vector()
> (6, 2, 0)
>
> however, the isotropic vector above is not isotropic anymore:
>
> sage: v=vector([1,a,1,0,0,0,0,0])
> sage: v*Q.matrix()*v
> sqrt(2)*(1.00*sqrt(2) - 1.41421356237310) - 
> 1.41421356237310*sqrt(2) + 2.00
>
> I also tried to define 
>
> sage: a=sqrt(AA(2))
> sage: 
> Q=QuadraticForm(AA,8,[1/2,-a/2,0,0,0,0,0,0,1/2,-a/2,0,0,0,0,0,1/2,-1/2,0,0
> : ,0,0,1/2,-1/2,0,0,0,1/2,-1/2,0,0,1/2,-a/2,0,1/2,-a/2,1/2])
>
> but Q.signature_vector() gives a runtime error with many lines of code 
> ending in:
>
> RuntimeError: maximum recursion depth exceeded
>
>
> Questions:
> 1) is Q.signature_vector() over cyclotomic field is interpreted in some 
> other way than for reals, thus making the result (8,0,0) somehow correct?
>
> 2) Which setting would guarantee both the correct result for 
> signature_vector() using the exact arithmetic and at the same time show 
> that v is actually an isotropic vector?
>
> Thank you!
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/32d8c813-7d58-4cf8-aaa0-1ea25f7b03b1%40googlegroups.com.