#13250: Additional poset examples
---------------------------------+------------------------------
       Reporter:  csar           |         Owner:  sage-combinat
           Type:  enhancement    |        Status:  needs_review
       Priority:  major          |     Milestone:  sage-5.11
      Component:  combinatorics  |    Resolution:
       Keywords:  sd40           |     Merged in:
        Authors:                 |     Reviewers:
Report Upstream:  N/A            |   Work issues:
         Branch:                 |  Dependencies:
       Stopgaps:                 |
---------------------------------+------------------------------

Comment (by ncohen):

 ? Why do you say that it's correct ? Surely you agree that this mro thing
 is not something that the user should see ? And how renaming a method from
 `mro` to `_mro_` or `_the_method_that_used_to_be_called_mro_` could be a
 structural problem ? `O_o`

 Nathann

--
Ticket URL: <http://trac.sagemath.org/ticket/13250#comment:11>
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.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to