Re: [sage-devel] Status of the legacy Sage notebook

2018-08-15 Thread Timo Kaufmann
See https://trac.sagemath.org/ticket/25837 for discussion about deprecation. I think the documentation ticket is much smaller in scope and independent of deprecation. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this

Re: [sage-devel] Status of the legacy Sage notebook

2018-08-15 Thread François Bissey
> On 16/08/2018, at 10:04, John H Palmieri wrote: > > On ticket 25382, https://trac.sagemath.org/ticket/25382, the following > questions have been raised: > > - Is the old Sage notebook deprecated? > > - If not, should it be? > > - In any case, the documentation builds with Python 2. It

[sage-devel] Status of the legacy Sage notebook

2018-08-15 Thread John H Palmieri
On ticket 25382, https://trac.sagemath.org/ticket/25382, the following questions have been raised: - Is the old Sage notebook deprecated? - If not, should it be? - In any case, the documentation builds with Python 2. It does not build (because sagenb is not Python 3 compatible) with Python 3.

Re: [sage-devel] PEP idea: unary division

2018-08-15 Thread rjf
Eric says *I'm all for more operators supported by syntax* This sounds like a terrible idea to me. I assume you do not endorse ALL operators. Just look at the machine-level operations available in a typical CPU. Also look at the kinds of syntax freely invented by physicists, chemists, and

Re: [sage-devel] OS X build failure: "Error installing package gfortran-7.2.0"

2018-08-15 Thread François Bissey
That looks like a symptom of not installing (or re-installing after an upgrade) the xcode command line tools. François > On 16/08/2018, at 07:51, Jeremy Martin wrote: > > I am trying to install sage 8.3 from source, running MacOS 10.13.6 High > Sierra. A snippet of the output is below. I'm

[sage-devel] Parallelization issue on macOS

2018-08-15 Thread Eric Gourgoulhon
Hi, Various Sage users have reported on that parallelization of tensor field computations does not work on macOS. The latest report, yesterday on sagemanifolds.list: https://sympa.obspm.fr/wws/arc/sagemanifolds.list/2018-08/msg3.html says that this example notebook

[sage-devel] Re: Start a Sage session from a session of its own Python interpreter ?

2018-08-15 Thread Pedro Cruz
>>> from sage.all import * >>> exec(preparse(r""" ... a = 2^3 ... print a ... """))8>>> a8>>> exit> py$a8 or also: >>> load("some.sage") #I believe all sage power is available in load() but not >>> all in exec(preparse()). segunda-feira, 13 de Agosto de 2018 às 18:07:41 UTC+1, Emmanuel

[sage-devel] Re: OS X build: "sorry, unimplemented: 64-bit mode not compiled in"

2018-08-15 Thread Bernie Walp
Thanks, Dima! You nailed my problem. Yes, I did not have “gfortran”. Sage 8.3 built itself without trouble after I installed gfortran (and ran "configure" before make) https://gcc.gnu.org/wiki/GFortranBinaries#MacOS Thanks again, Bernie W. On Tuesday, August 14, 2018 at 1:10:11 AM

Re: [sage-devel] misleading comment on cygwin binaries

2018-08-15 Thread Jeroen Demeyer
On 2018-08-14 23:43, Erik Bray wrote: Isn't that just the normal message when running `sage -sh`? IIRC, I added that text because people were generally quite confused which kind of commands should be run inside or outside of a Sage shell. The top-level "make" commands are typically run

Re: [sage-devel] issue with cos(pi/2) and sin(pi)

2018-08-15 Thread David Coudert
> Le 14 août 2018 à 20:37, TB a écrit : > > Because float(pi/2) is not exactly pi/2: > > sage: n(pi/2 - float(pi/2), 53) > 0.000 > sage: n(pi/2 - float(pi/2), 54) # also for perc > 54 of course > 1.11022302462516e-16 and what’s the advantage of numerical_approx(v, digits=10) over