[sage-devel] Re: sage 6.6 & pyopenssl

2015-05-03 Thread leif
Clemens Heuberger wrote: > I tried to install pyopenssl in order to run sagenb in sage 6.6 with > secure=True. It fails with Error 404, see below. > > Regards, > > CH > > I get: > $ ./sage -i pyopenssl > Attempting to download package pyopenssl Checking online list of optional packages. > [

[sage-devel] Re: sage 6.6 & pyopenssl

2015-05-03 Thread leif
Volker Braun wrote: > Use "sage -pip install pyopenssl" That's not what currently 'make ssl' does, nor what README.txt says: 10. OPTIONAL: Read this if you are intending to run a Sage notebook server for multiple users. For security (i.e., to run "notebook(secure=True)") you want to acces

[sage-devel] Re: Change of semantics for 'show'

2015-05-03 Thread Volker Braun
On Thursday, April 30, 2015 at 8:19:39 AM UTC+2, Martin R wrote: > > I'm only trying to understand. Yes, I assume it happens that someone is > using sage as a python library and then possibly only wants repr. > If you use Sage as a Python library then you are in control of the displayhook. The

[sage-devel] Re: src/bin in path?

2015-05-03 Thread Volker Braun
IMHO the question really is about "what constitutes a binary install". Presumably the answer is something like "the sage launcher script, and the SAGE_LOCAL tree". This is not true right now, and IMHO there are bigger fish to fry than $PATH. For example, the documentation output is in src/doc.

[sage-devel] Re: sage 6.6 & pyopenssl

2015-05-03 Thread Volker Braun
Use "sage -pip install pyopenssl" On Sunday, May 3, 2015 at 4:03:01 PM UTC+2, Clemens Heuberger wrote: > > I tried to install pyopenssl in order to run sagenb in sage 6.6 with > secure=True. It fails with Error 404, see below. > > Regards, > > CH > > I get: > $ ./sage -i pyopenssl > Attempti

[sage-devel] sage 6.6 & pyopenssl

2015-05-03 Thread Clemens Heuberger
I tried to install pyopenssl in order to run sagenb in sage 6.6 with secure=True. It fails with Error 404, see below. Regards, CH I get: $ ./sage -i pyopenssl Attempting to download package pyopenssl >>> Checking online list of optional packages. [.] >>> Found pyopenssl-0.13.p0 >>> Trying to dow

[sage-devel] Re: Bug in pickling of callable symbolic functions

2015-05-03 Thread Eric Gourgoulhon
Hi, Le vendredi 1 mai 2015 17:23:55 UTC+2, Nils Bruin a écrit : > > On Friday, May 1, 2015 at 2:00:11 AM UTC-7, Eric Gourgoulhon wrote: > > >> Thanks for your answer. There is no predefined 'H' function in Sage, so >> do you mean a nameclash with a predefined function 'H' in Pynac ? Which >> f

[sage-devel] Re: dimension() broken for ideals?

2015-05-03 Thread mmarco
It is definitely a bug in the dimension method. If singular can handle the ring, sage asks singular to compute the dimension, which does correctly (the -1 is the singular convention for empty varieties). The problem is that when the field is not supported by singular (which happens with QQbar

Re: [sage-devel] Is CMake OK for a standard spkg?

2015-05-03 Thread Dima Pasechnik
On Saturday, 2 May 2015 08:25:15 UTC+1, Isuru Fernando wrote: > > Hi, > > What is the consensus on getting CMake into Sage? > > I made a ticket to get CMake into the optional packages list. > http://trac.sagemath.org/ticket/18078 > , so that CMake can be