Re: [sage-devel] Sage 9.3 release cycle

2020-11-10 Thread Vincent Delecroix
Le 11/11/2020 à 08:41, Dima Pasechnik a écrit : On Wed, 11 Nov 2020, 07:38 Vincent Delecroix, <20100.delecr...@gmail.com> wrote: Dear all, Among the "package upgrades", I want to emphasize the one to pari 2.13 (see https://trac.sagemath.org/ticket/30801). is anyone working to fix the rem

Re: [sage-devel] Sage 9.3 release cycle

2020-11-10 Thread Dima Pasechnik
On Wed, 11 Nov 2020, 07:38 Vincent Delecroix, <20100.delecr...@gmail.com> wrote: > Dear all, > > Among the "package upgrades", I want to emphasize the one > to pari 2.13 (see https://trac.sagemath.org/ticket/30801). > is anyone working to fix the remaining issues there? The debian freeze is happ

Re: [sage-devel] Sage 9.3 release cycle

2020-11-10 Thread Vincent Delecroix
Dear all, Among the "package upgrades", I want to emphasize the one to pari 2.13 (see https://trac.sagemath.org/ticket/30801). The debian freeze is happening soon and the pari ticket is somehow blocking the SageMath update. Would make sense to have Sage 9.3 released by then. Le 10/11/2020 à 23:1

[sage-devel] Re: Sage 9.3 release cycle

2020-11-10 Thread Matthias Koeppe
On Tuesday, November 10, 2020 at 2:14:29 PM UTC-8, Matthias Koeppe wrote: > > I would suggest that we aim for a much shorter release cycle for Sage 9.3 > with a focus on the following issues: > - macOS 11 Big Sur > - critical fixes that were not merged in 9.2 > - package upgrades that did not make

[sage-devel] Sage 9.3 release cycle

2020-11-10 Thread Matthias Koeppe
I would suggest that we aim for a much shorter release cycle for Sage 9.3 with a focus on the following issues: - macOS 11 Big Sur - critical fixes that were not merged in 9.2 - package upgrades that did not make it into 9.2 - fixing broken optional packages Perhaps a release date at the end of t

Re: [sage-devel] How do I report a bug in Sage 9.2 (app version) for macOS?

2020-11-10 Thread Dima Pasechnik
Anaconda is a different serpent :-) I don't think it was tested, no idea if it would work. If you install miniconda, it will go to /opt/miniconda3/ - so it's a different tree. On Tue, Nov 10, 2020 at 7:09 PM Murray Eisenberg wrote: > > How does one use the conda binaries instead? > > On 10 Nov202

Re: [sage-devel] How do I report a bug in Sage 9.2 (app version) for macOS?

2020-11-10 Thread Isuru Fernando
Is your firewall blocking https://conda.anaconda.org/conda-forge/noarch/_r-mutex-1.0.1-anacondar_1.tar.bz2 ? Isuru On Tue, Nov 10, 2020 at 1:09 PM Murray Eisenberg wrote: > I get an unexpected error doing that (with conda/anaconda already > installed): > > # >> ERROR REPORT

Re: [sage-devel] How do I report a bug in Sage 9.2 (app version) for macOS?

2020-11-10 Thread Murray Eisenberg
I get an unexpected error doing that (with conda/anaconda already installed): # >> ERROR REPORT << Traceback (most recent call last): File "/opt/anaconda3/lib/python3.8/site-packages/conda/exceptions.py", line 1079, in __call__ return fun

Re: [sage-devel] How do I report a bug in Sage 9.2 (app version) for macOS?

2020-11-10 Thread Murray Eisenberg
How does one use the conda binaries instead? > On 10 Nov2020, at 12:15 PM, Dima Pasechnik wrote: > > On Tue, Nov 10, 2020 at 5:12 PM Samuel Lelievre > mailto:samuel.lelie...@gmail.com>> wrote: >> >> 2020-11-10 15:46:13 UTC, Murray Eisenberg: >>> >>> This concerns the missing openssl for python

Re: [sage-devel] Re: How do I report a bug in Sage 9.2 (app version) for macOS?

2020-11-10 Thread Matthias Koeppe
On Tuesday, November 10, 2020 at 9:15:26 AM UTC-8, Dima Pasechnik wrote: > > > I'd just stop recommending the use of our macOS binaries until the > signing issue is solved. > Use Conda. > > +1. In fact, I would suggest that we stop publishing macOS binaries until then. -- You received t

Re: [sage-devel] Re: How do I report a bug in Sage 9.2 (app version) for macOS?

2020-11-10 Thread Dima Pasechnik
On Tue, Nov 10, 2020 at 5:12 PM Samuel Lelievre wrote: > > 2020-11-10 15:46:13 UTC, Murray Eisenberg: > > > > This concerns the missing openssl for python3, > > which prevents the jupyter server from starting > > under macOS Catalina 10.15.7. > > > > How/where report this as a bug? > > The current

Re: [sage-devel] How do I report a bug in Sage 9.2 (app version) for macOS?

2020-11-10 Thread Dima Pasechnik
I can only lament about the sorry state of macOS binaries support for 9.2 on macOS 10.15.7. I get “python3.8” cannot be opened because the developer cannot be verified. already in a terminal session. What works for me, totally hassle-free, is Conda. See https://doc.sagemath.org/html/en/installa

[sage-devel] Re: How do I report a bug in Sage 9.2 (app version) for macOS?

2020-11-10 Thread Samuel Lelievre
2020-11-10 15:46:13 UTC, Murray Eisenberg: > > This concerns the missing openssl for python3, > which prevents the jupyter server from starting > under macOS Catalina 10.15.7. > > How/where report this as a bug? The current licence of OpenSSL prevents us from shipping it. OpenSSL is changing its

[sage-devel] How do I report a bug in Sage 9.2 (app version) for macOS?

2020-11-10 Thread Murray Eisenberg
This concerns the missing openssl for python3, which prevents the jupyter server from starting under macOS Catalina 10.15.7. How/where report this as a bug? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop

Re: [sage-devel] Significant memory leak using mathematical constants

2020-11-10 Thread Dima Pasechnik
On Tue, Nov 10, 2020 at 9:42 AM Nils Bruin wrote: > > On Sunday, November 8, 2020 at 7:55:12 AM UTC-8, Dima Pasechnik wrote: >> >> thanks for a short example, it is helpful. >> now someone needs to dig into pynac code to understand where the memory leak >> is coming from. >> > I've commented on t

Re: [sage-devel] Significant memory leak using mathematical constants

2020-11-10 Thread Nils Bruin
On Sunday, November 8, 2020 at 7:55:12 AM UTC-8, Dima Pasechnik wrote: > > thanks for a short example, it is helpful. > now someone needs to dig into pynac code to understand where the memory > leak is coming from. > > I've commented on the ticket -- I have a pretty good candidate for where the l