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

2018-08-16 Thread Jeremy Martin
Thanks, François! That seems to have fixed it. -Jeremy On Wednesday, August 15, 2018 at 3:14:39 PM UTC-5, François Bissey wrote: > > 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, J

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

2018-08-16 Thread David Roe
On Fri, Jun 3, 2016 at 2:07 PM Jeroen Demeyer wrote: > On 2016-06-03 19:55, Simon King wrote: > > Note that testing "a==1" goes through the coercion model as well. > > Sure, but that's not what you want to do. I propose to test something like > > (isinstance(a, int) and a == 1) or (type(a) is Int

Re: [sage-devel] Adding a help() method to Sage objects?

2018-08-16 Thread Erik Bray
On Fri, Aug 10, 2018 at 9:48 PM Jeroen Demeyer wrote: > > On 2018-08-09 14:54, Erik Bray wrote: > > In principle, if classes had this, one might also want it for > > functions, but that's a little bit more problematic. > > I think that's already a bit problematic: whether something is a class > or

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

2018-08-16 Thread kcrisman
> https://trac.sagemath.org/ticket/25837, there are still numerous use > cases--especially cases of particular interest for math software--that > the SageNB still handles better than Jupyter. So any effort that > might be spent on SageNB is probably better spent improving those use > cases

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

2018-08-16 Thread Erik Bray
On Thu, Aug 16, 2018 at 2:50 PM Jeroen Demeyer wrote: > > On 2018-08-16 14:30, Erik Bray wrote: > > In the meantime I think we should remove that warning, or at least > > have a way to disable it, as it's clearly confusing to users. > > *NOT* having the warning is also confusing to users (that's w

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

2018-08-16 Thread Jeroen Demeyer
On 2018-08-16 14:30, Erik Bray wrote: In the meantime I think we should remove that warning, or at least have a way to disable it, as it's clearly confusing to users. *NOT* having the warning is also confusing to users (that's why it was added in the first place). So if the warning is not clea

[sage-devel] Repeat: Dropping support for old-style .spkgs?

2018-08-16 Thread Erik Bray
On Wed, Aug 8, 2018 at 7:06 PM Erik Bray wrote: > > We still have quite a bit of code around for supporting old-style > packages in .spkg archives, though it is not well tested anymore and > I'm not even 100% sure installing these still works. > > We have also noted, since Sage 6.9, that these are

Re: [sage-devel] Dropping support for old-style .spkgs?

2018-08-16 Thread Erik Bray
On Tue, Aug 14, 2018 at 8:45 PM Michael Orlitzky wrote: > > On 08/14/2018 12:54 PM, Erik Bray wrote: > > > > Why would they do even that? It's just a data package. For the > > purposes of upstream packaging it doesn't need a configure.ac. It can > > just be a bundle of files. But I still don't

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

2018-08-16 Thread Erik Bray
On Wed, Aug 15, 2018 at 11:08 AM Jeroen Demeyer wrote: > > 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 Sa

Re: [sage-devel] Parallelization issue on macOS

2018-08-16 Thread Erik Bray
On Thu, Aug 16, 2018 at 10:27 AM Jeroen Demeyer wrote: > > On 2018-08-15 17:46, Eric Gourgoulhon wrote: > > Various Sage users have reported on that parallelization of tensor field > > computations does not work on macOS. > > This might be https://trac.sagemath.org/ticket/25921 > > Does it help to

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

2018-08-16 Thread Erik Bray
On Thu, Aug 16, 2018 at 12:07 AM François Bissey wrote: > > > > > 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

[sage-devel] installation fortran

2018-08-16 Thread Dima Pasechnik
to see what's wrong, look in /home/m/Bureau/sage-8.3/logs/pkgs/gfortran-7.2.0.log (or post it here) but the easiest would be to install the system's gfortran. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and sto

[sage-devel] installation fortran

2018-08-16 Thread Mathieu Roux
Hello, I have just tried to build sage from sources, but if failed. I use linux mint cinnamon (last version). Thanks [gfortran-7.2.0] [gfortran-7.2.0] Error installing package gfortran-7.2.0 [gfortran-7.2.0] *

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

2018-08-16 Thread Dima Pasechnik
Basically, unless anyone with need, time, and knowledge to maintain sagenb steps forward, it should be deprecated and removed. Or funds found to pay someone to do this work. I stopped using sagenb ages ago, and have much better ways to use my time. On Thursday, August 16, 2018 at 12:01:16 PM UT

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

2018-08-16 Thread Dima Pasechnik
There is nobody with enough knowledge of the guts of sagenb to maintain it, and frankly the sooner it is deprecated and removed, the better. On Thursday, August 16, 2018 at 1:04:32 AM UTC+3, John H Palmieri wrote: > > On ticket 25382, https://trac.sagemath.org/ticket/25382, the following > quest

Re: [sage-devel] Parallelization issue on macOS

2018-08-16 Thread Jeroen Demeyer
On 2018-08-15 17:46, Eric Gourgoulhon wrote: Various Sage users have reported on that parallelization of tensor field computations does not work on macOS. This might be https://trac.sagemath.org/ticket/25921 Does it help to set the environment variable OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES