#19963: Build documentation in $SAGE_SHARE/doc/sage
-------------------------------------+-------------------------------------
       Reporter:  jdemeyer           |        Owner:
           Type:  enhancement        |       Status:  needs_review
       Priority:  major              |    Milestone:  sage-7.1
      Component:  build              |   Resolution:
       Keywords:                     |    Merged in:
        Authors:  Jeroen Demeyer     |    Reviewers:
Report Upstream:  N/A                |  Work issues:
         Branch:                     |       Commit:
  u/jdemeyer/build_documentation_in__sage_local_share_doc_sage|  
de10a5ed704bac161fa3f43d381cd3aac0776817
   Dependencies:  #19127             |     Stopgaps:
-------------------------------------+-------------------------------------

Comment (by fbissey):

 In `sage_setup/docbuild/__init__.py` we currently have at line 101 and
 after
 {{{
         if 'output/html' in output_dir:
             logger.warning("Build finished. The built documents can be
 found in %s",
                            output_dir)
         elif 'output/pdf' not in output_dir:
             logger.info("Build finished. The built documents can be found
 in %s",
                            output_dir)
         else:
             logger.info("LaTeX file written to %s; now making PDF.",
                            output_dir)
 }}}
 Will we ever see a message "Build finished. The built documents can be
 found in..." again?

--
Ticket URL: <http://trac.sagemath.org/ticket/19963#comment:15>
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to