#11080: move notebook to flask/wsgi-based notebook
-----------------------------------------------------------------------+----
       Reporter:  jason                                                |        
 Owner:                                                
           Type:  enhancement                                          |        
Status:  needs_work                                    
       Priority:  blocker                                              |     
Milestone:  sage-5.1                                      
      Component:  notebook                                             |    
Resolution:                                                
       Keywords:  sd31 sd35.5                                          |   Work 
issues:                                                
Report Upstream:  N/A                                                  |     
Reviewers:  Rado Kirov, Dan Drake, Jason Grout, Simon King
        Authors:  Mike Hansen, Rado Kirov, William Stein, Jason Grout  |     
Merged in:                                                
   Dependencies:  #11078, #11874, #12229, #11503, #12327               |      
Stopgaps:                                                
-----------------------------------------------------------------------+----
Changes (by SimonKing):

  * reviewer:  Rado Kirov, Dan Drake, Jason Grout => Rado Kirov, Dan Drake,
               Jason Grout, Simon King


Comment:

 Above, I had claimed that pkg-config did not recognise the headers
 installed by the optional openssl spkg. I stand corrected, since inside a
 sage shell I get
 {{{
 (sage-sh) king@mpc622:sage-5.1.notebook$ pkg-config --cflags openssl
 -I/mnt/local/king/SAGE/experiment/notebook/sage-5.1.notebook/local/include
 }}}

 So, testing for the presence of openssl using pkg-config ''during
 configuration'' (i.e., before starting the installation) makes sense.

 If it is true that sagenb would - in principle - also work without
 openssl, I agree with ppurka that we could easily avoid openssl to become
 de-facto standard:

  * Make sure that sagenb spkg installs and the notebook basically works,
 even if openssl is not installed. Of course, the notebook will then lack
 some features.
  * If one tries to use the openid and https features, then a runtime error
 should be raised, with a clear error message along the lines
  {{{
 Install openssl with development headers. If they are not available for
 your operating system, you could install the optional openssl Sage
 package.
 This is possible, e.g., with the command
    install_package("openssl")
 during a Sage session.
 Then, re-install the Sage notebook package, e.g., by
    install_package("sagenb", forced=True)
 during a Sage session.
  }}}

 Would that be enough, actually? Or would a recompilation of Sage be needed
 after re-installation of sagenb?

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11080#comment:247>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to