#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 tscrim):
Replying to [comment:7 ncohen]:
> Hmmmmm... Well, what I wondered about is what was such a method (with a
shortened name, while we would usually write "method_resolution_order")
was doing in Poset. I mean, not in Poset, but as it really is related to
Sage's implementation of whatever it implements more than to what the
Poset means as a mathematical object, I thought that we would have stuck
with `_mro_` instead. Hidden function, as user don't care much `O_o`
But you're neglecting the fact that this is a class, which 98% of the time
in python you are not manipulating other than `isinstance(obj, cls)`. So
having this class `posets` is not the truly pythonic way, instead it
should be at the module level (because this is not Java where everything
has to be [in] a class). But if you are going to insist on changing that,
it should be done on a separate ticket.
--
Ticket URL: <http://trac.sagemath.org/ticket/13250#comment:8>
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.
