#9128: Sphinx should be aware of all.py to find its links
------------------------------+---------------------------------------------
   Reporter:  hivert          |       Owner:  hivert      
       Type:  enhancement     |      Status:  needs_review
   Priority:  major           |   Milestone:  sage-4.4.4  
  Component:  documentation   |    Keywords:  Sphinx links
     Author:  Florent Hivert  |    Upstream:  N/A         
   Reviewer:                  |      Merged:              
Work_issues:                  |  
------------------------------+---------------------------------------------

Comment(by hivert):

 > It may be a good idea not to give warnings in such cases, but on the
 other hand it is probably quite rare and there is no need to make logic of
 this patch more convoluted. (In my case the docstring of one of the
 functions says "see the source code of ... for more involved examples",
 since those examples cannot be easily written as standalone code and I
 didn't want to write something "involved, but artificial.")

 Can you describe more precisely what's happening ? Maybe with a very small
 example... I'm not sure to understand what you are doing... I have the
 impression that you are requesting me to remove warnings about private
 methods (i.e.: starting with underscore).

 > Since I really like this functionality, I will continue using your patch
 (and its fresh versions if they become available) and report new problems,
 if there will be any. But for the final review we will need someone else,
 since I don't know how Sphinx works and cannot comment on the code itself.

 I'll try to ping some on sage-devel.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9128#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 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