[sage-devel] Re: Minimum Python version to 3.8

-1. Even NEP 29 (https://numpy.org/neps/nep-0029-deprecation_policy.html) does not drop Python 3.7 support before end of the year. On Monday, May 10, 2021 at 4:12:48 PM UTC-7 Travis Scrimshaw wrote: > On #30423 , which is getting > close to completion, w

Re: [sage-devel] Minimum Python version to 3.8

On Tue, 11 May 2021, 00:51 'Travis Scrimshaw' via sage-devel, < sage-devel@googlegroups.com> wrote: > Do we have a doctest tag for a minimum python version? > make your own, say: # optional: py38 > Best, > Travis > > > On Tuesday, May 11, 2021 at 9:20:00 AM UTC+10 dim...@gmail.com wrote: > >>

Re: [sage-devel] Minimum Python version to 3.8

Do we have a doctest tag for a minimum python version? Best, Travis On Tuesday, May 11, 2021 at 9:20:00 AM UTC+10 dim...@gmail.com wrote: > On Tue, May 11, 2021 at 12:12 AM 'Travis Scrimshaw' via sage-devel > wrote: > > > > On #30423, which is getting close to completion, we will be using > m

Re: [sage-devel] Proposal: Very short release cycle for Sage 9.4

We should also update GAP and start using gappy. On Tue, May 11, 2021 at 12:36 AM François Bissey wrote: > > I guess I could whip up a branch quickly since we know the things that have > to be done overall. > I would prefer if we had a new pynac release rather than continue pilling > patches. >

Re: [sage-devel] Proposal: Very short release cycle for Sage 9.4

I guess I could whip up a branch quickly since we know the things that have to be done overall. I would prefer if we had a new pynac release rather than continue pilling patches. François > On 11/05/2021, at 11:00, 'Travis Scrimshaw' via sage-devel > wrote: > > +1 on this. I know many people

Re: [sage-devel] Minimum Python version to 3.8

On Tue, May 11, 2021 at 12:12 AM 'Travis Scrimshaw' via sage-devel wrote: > > On #30423, which is getting close to completion, we will be using > multiprocessing.shared_memory, which is only available on Python 3.8+. > However, right now we are at least allowing Python 3.7 (as per the patchbot).

[sage-devel] Minimum Python version to 3.8

On #30423 , which is getting close to completion, we will be using multiprocessing.shared_memory, which is only available on Python 3.8+. However, right now we are at least allowing Python 3.7 (as per the patchbot). So my main proposal would be to bump the

[sage-devel] Re: Proposal: Very short release cycle for Sage 9.4

+1 on this. I know many people who use the latest OSX. Best, Travis On Tuesday, May 11, 2021 at 5:09:55 AM UTC+10 Matthias Koeppe wrote: > ... with a focus on adding support for gcc/gfortran 11 ( > https://trac.sagemath.org/ticket/31786) > and in particular fixing the build on macOS Big Sur wit

Re: [sage-devel] [abi:cxx11] in givaro prevents linking to system givaro on Fedora 32

On Mon, 10 May 2021, 21:49 Volker Braun, wrote: > "Dual" refers to libstdc++ here, i.e. you only have one standard library > supporting both abi's. > > Other libraries generally are only one or the other, this is what is > controlled by the -D_GLIBCXX_USE_CXX11_ABI; Theoretically you could make >

Re: [sage-devel] [abi:cxx11] in givaro prevents linking to system givaro on Fedora 32

"Dual" refers to libstdc++ here, i.e. you only have one standard library supporting both abi's. Other libraries generally are only one or the other, this is what is controlled by the -D_GLIBCXX_USE_CXX11_ABI; Theoretically you could make your own dual-abi library but you'd have to plaster __

[sage-devel] Re: Building Sage 9.3 on Mac fails due to numpy

Just as a followup, I did confirm on my Big Sur that the steps I outlined above does let sage build. On Monday, May 10, 2021 at 3:52:20 PM UTC-4 Matthias Koeppe wrote: > Yes, using gcc@10 from homebrew should be a good option too. I have added > this suggestion to to > https://wiki.sagemath.o

[sage-devel] Re: Building Sage 9.3 on Mac fails due to numpy

Yes, using gcc@10 from homebrew should be a good option too. I have added this suggestion to to https://wiki.sagemath.org/ReleaseTours/sage-9.3#Availability_of_Sage_9.3_and_installation_help (it may need expanding) On Monday, May 10, 2021 at 12:28:50 PM UTC-7 zsc...@gmail.com wrote: > sorry

[sage-devel] Re: Building Sage 9.3 on Mac fails due to numpy

On Monday, May 10, 2021 at 12:27:19 PM UTC-7 modp...@gmail.com wrote: > Thanks for the info. But I don't fully get what I should try. The link you > have is just a link to the ticket. I do not see what are the steps one need > to take for building 9.3 on Mac succesfully. > Can you outline it her

[sage-devel] Re: Building Sage 9.3 on Mac fails due to numpy

sorry, that should be `brew install gcc@10` On Monday, May 10, 2021 at 3:27:47 PM UTC-4 Zachary Scherr wrote: > I haven't fully tested this yet, but you can also try installing gcc-10 > through homebrew and then using gfortran-10. Here are the steps to try: > > > brew install gcc-10 > > and the

[sage-devel] Re: Building Sage 9.3 on Mac fails due to numpy

I haven't fully tested this yet, but you can also try installing gcc-10 through homebrew and then using gfortran-10. Here are the steps to try: > brew install gcc-10 and then once in a clean sage directory (so run make distclean if you need to): > source .homebrew-build-env > make configure >

[sage-devel] Re: Building Sage 9.3 on Mac fails due to numpy

Thanks for the info. But I don't fully get what I should try. The link you have is just a link to the ticket. I do not see what are the steps one need to take for building 9.3 on Mac succesfully. Can you outline it here? On Monday, May 10, 2021 at 9:01:56 PM UTC+2 Matthias Koeppe wrote: > Our c

[sage-devel] Proposal: Very short release cycle for Sage 9.4

... with a focus on adding support for gcc/gfortran 11 (https://trac.sagemath.org/ticket/31786) and in particular fixing the build on macOS Big Sur with homebrew that was broken by homebrew's upgrade to gcc 11 (https://trac.sagemath.org/ticket/29703). -- You received this message because you

[sage-devel] Re: Building Sage 9.3 on Mac fails due to numpy

Our configure script rejects the current gfortran from homebrew - which is already 11.1. This leads to building gfortran from source, an old version which does not support Big Sur. Try with https://trac.sagemath.org/ticket/29703 please (use ./bootstrap), which upgrades our gcc/gfortran package

Re: [sage-devel] [abi:cxx11] in givaro prevents linking to system givaro on Fedora 32

On Sunday, May 9, 2021 at 11:28:30 AM UTC+1 Volker Braun wrote: > PS: Fedora 32 EOL is imminent (= 4 weeks after the just-released fedora > 34), so I wouldn't worry too much about it > Our IT just updated this machine for me, from a long EOLed Fedora, to Fedora 32. I just asked them to make

Re: [sage-devel] [abi:cxx11] in givaro prevents linking to system givaro on Fedora 32

On Sunday, May 9, 2021 at 11:24:23 AM UTC+1 Volker Braun wrote: > This is c++11 dual abi, see > https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html > > IMHO we just shouldn't use the system version then, but building Sage with > -D_GLIBCXX_USE_CXX11_ABI=0 should allow you to li