https://groups.google.com/d/forum/sage-develsage-develThis email list is for discussion of Sage (<a href="http://www.sagemath.org">www.sagemath.org</a>) development issues. This list usually has heavy traffic.Google GroupsDima Pasechnik2021-05-17T09:32:59Zhttps://groups.google.com/d/topic/sage-devel/ti1qM7scoiQRe: [sage-devel] ptestlong failures Sage-9.3source: > > ---------------------------------------------------------------------- > sage -t --long --warn-long 103.3 --random-seed=0 src/sage/calculus/riemann.pyx # Killed due to illegal instruction this kind of error indicates that a component is using CPU instructions not understood byJose Antonio Medrano Garcia2021-05-17T04:33:55Zhttps://groups.google.com/d/topic/sage-devel/FjCg0U17NDcBug in Sage 9.2 when trying to plot a simple graphHello, I just installed Sage 9.2 with Windows installer 0.6.2 and I got this error when trying to plot a very simple graph using plot() ------------------------------------------------------------------------ Unhandled SIGSEGV: A segmentation fault occurred. This probably occurred because aMatthias Koeppe2021-05-17T02:18:44Zhttps://groups.google.com/d/topic/sage-devel/YlqimapHYdkRe: Python 3.6On Sunday, May 16, 2021 at 1:14:27 PM UTC-7 vdelecroix wrote: > 2. Did we plan the end of Python 3.6 support in Sage? Support of system Python 3.6 is already deprecated for the Sage distribution in Sage 9.3 (https://trac.sagemath.org/ticket/31318). Many major packages follow NEP 29 (https://traDima Pasechnik2021-05-16T20:45:42Zhttps://groups.google.com/d/topic/sage-devel/YlqimapHYdkRe: [sage-devel] Python 3.6On Sun, 16 May 2021, 21:14 Vincent Delecroix, <20100.d...@gmail.com> wrote: > Dear all, > > Python 3.6 is supposed to be supported for Sage (e.g. the > build system accepts Python 3.6 from the system). This > version of Python 3.6 which reach its end of life on > December this year. I sent anvdelecroix2021-05-16T20:14:27Zhttps://groups.google.com/d/topic/sage-devel/YlqimapHYdkPython 3.6Dear all, Python 3.6 is supposed to be supported for Sage (e.g. the build system accepts Python 3.6 from the system). This version of Python 3.6 which reach its end of life on December this year. I sent an e-mail not long ago about sage not fully supporting Python 3.6. I did setup a patchbotRichard_L2021-05-16T15:26:36Zhttps://groups.google.com/d/topic/sage-devel/ti1qM7scoiQptestlong failures Sage-9.3'make ptestlong' gave the following error summary on a new build from source: ---------------------------------------------------------------------- sage -t --long --warn-long 103.3 --random-seed=0 src/sage/calculus/riemann.pyx # Killed due to illegal instruction sage -t --long --warn-long 103.3Emmanuel Charpentier2021-05-16T12:44:12Zhttps://groups.google.com/d/topic/sage-devel/ERFOhACN5q8Re: missing '^' logical operator : bug (oversight) or design ?Thank you very much ! I didn't know that. I note that this information is a bit difficult to reach in the documentation... and tha, in my Sage installation (from git tree, on Debian testing), "search_doc" is broken. Le dimanche 16 mai 2021 à 09:51:39 UTC+2, Nils Bruin a écrit : > If the preparserNils Bruin2021-05-16T07:51:39Zhttps://groups.google.com/d/topic/sage-devel/ERFOhACN5q8Re: missing '^' logical operator : bug (oversight) or design ?If the preparser is active in sage (and it is by default if you run sage in its normal, interactive way or if you use *.sage files) then the substitution "^" -> "**" is made. Hence, the error message that you see: python is complaining about "**" as an unsupported operand type, not "^". TheEmmanuel Charpentier2021-05-16T06:09:35Zhttps://groups.google.com/d/topic/sage-devel/ERFOhACN5q8missing '^' logical operator : bug (oversight) or design ?Dear list, consider python : >>> a = set(['a', 'b', 'c']) >>> b = set(['b', 'c', 'd']) >>> a & b {'b', 'c'} >>> a | b {'b', 'a', 'd', 'c'} >>> a - b {'a'} >>> a ^ b {'a', 'd'} vs Sage : sage: a = set(['a', 'b', 'c']) sage: b = set(['b', 'c', 'd']) sage: a & b {'b', 'c'} sage: a | b {'a',Jan Groenewald2021-05-15T12:33:10Zhttps://groups.google.com/d/topic/sage-devel/_mbZiUBgdDkRe: [sage-devel] problem building maximaHi On Fri, 14 May 2021 at 15:05, Dima Pasechnik <dim...@gmail.com> wrote: > Thanks. Indeed, libffi is alive and well: > > ... > checking for ffi_closure_alloc in -lffi... yes > checking ffi/ffi.h usability... no > checking ffi/ffi.h presence... no > checking for ffi/ffi.h... no > checking ffi.hDima Pasechnik2021-05-15T10:35:53Zhttps://groups.google.com/d/topic/sage-devel/OGPadotHELgRe: [sage-devel] Re: Minimum Python version to 3.8On Sat, May 15, 2021 at 12:19 AM 'Travis Scrimshaw' via sage-devel <sage-...@googlegroups.com> wrote: > > Thank you for the pointer for how to add the optional marker. Adding a dummy spkg for when the Python version is sufficiently large feels like a much more invasive hack around by going intoTravis Scrimshaw2021-05-14T23:18:58Zhttps://groups.google.com/d/topic/sage-devel/OGPadotHELgRe: [sage-devel] Re: Minimum Python version to 3.8Thank you for the pointer for how to add the optional marker. Adding a dummy spkg for when the Python version is sufficiently large feels like a much more invasive hack around by going into the build system. ;) Jonathan, yes, that is how we can fix the code. The problem as I recall is theMatthias Koeppe2021-05-14T23:01:02Zhttps://groups.google.com/d/topic/sage-devel/KSLmpQGj9xkRe: [sage-devel] Re: test failures with buckygen (optional package)On Friday, May 14, 2021 at 12:23:49 PM UTC-7 vdelecroix wrote: > 1. sage-9.3 claims that it supports Python 3.6. My system Python > was by the way accepted by sage configure script. It did also warn you that using system python 3.6 is deprecated. > 2. the part of sage source code that IJonathan Kliem2021-05-14T20:57:39Zhttps://groups.google.com/d/topic/sage-devel/p7dYOW29PCIRe: [sage-devel] Re: Memory leak with matrices and finite fieldsIts the same code in the Main line. Sorry for the confusion. I googled it and that is how I found the exact place where this is defined. What I linked is how it looks now accounting for changes in gmp 6.2. Flint 2.6.3 has it but not 2.5.2.On May 14, 2021 10:31 PM, Dima Pasechnik < dim...@gmail.coDima Pasechnik2021-05-14T20:32:10Zhttps://groups.google.com/d/topic/sage-devel/p7dYOW29PCIRe: [sage-devel] Re: Memory leak with matrices and finite fieldsOn Fri, May 14, 2021 at 4:03 PM 'jonatha...@googlemail.com' via sage-devel <sage-...@googlegroups.com> wrote: > > I think I tracked it down. > > https://github.com/BrianGladman/flint/blob/trunk/gmpcompat.h this is a fork, dealing with Windows support of Flint. We should be working with