#11490: Add a thematic tutorial on coercion and categories
---------------------------------------------------------+------------------
       Reporter:  SimonKing                              |         Owner:  
mvngu                              
           Type:  enhancement                            |        Status:  
needs_review                       
       Priority:  major                                  |     Milestone:  
sage-5.7                           
      Component:  documentation                          |    Resolution:       
                              
       Keywords:  categories coercion thematic tutorial  |   Work issues:       
                              
Report Upstream:  N/A                                    |     Reviewers:  
Vincent Delecroix, Travis Scrimshaw
        Authors:  Simon King                             |     Merged in:       
                              
   Dependencies:  #14084                                 |      Stopgaps:       
                              
---------------------------------------------------------+------------------

Comment (by SimonKing):

 Replying to [comment:41 dimpase]:
 > > Do you really think this is not enough?
 > >
 >
 > The confusion comes from the fact that you explain the code '''before'''
 showing the code (or at least saying that it is coming).

 OK, then it is similar to pure maths: First show the theorem and then the
 proof. Actually, I tend to present a chain of thoughts that eventually
 constitutes the proof of a theorem that is only formulated ''after'' the
 proof. I'll try to change that.

 > There is also an inconsistency in the exposition, as you have the line
 > {{{
 > sage: from sage.rings.ring import Field
 > }}}
 > but no similar line for {{{UniqueRepresentation}}}.

 I explicitly imported Field, because this is what one needs to do when
 writing a module. So, I agree I should do the same with
 `UniqueRepresentation`.

 > After some trial and error upon reading [http://sphinx-
 doc.org/markup/code.htm Sphinx manual],
 > I found that the following will work with sphinx in Sage:
 > {{{
 > .. highlight:: python
 >    :linenothreshold: 2
 >
 > ::
 >
 >    x = 2
 >    y = [1,2]
 >    x = y
 >
 > .. highlight:: python
 >    :linenothreshold: 22222
 >
 > }}}
 > the 1st {{{highlight::}}} turns on line numberings for fragments with 2
 or more lines, and the 2nd {{{highlight::}}} effectively turns it off.

 Cool, thank you!

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11490#comment:42>
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 http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to