#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):
Yooooooooooo !
> 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). And if you are going to insist on changing that,
it should be done on a separate ticket.
I'm sorry but I don't get a word of what you say `O_o`
My question is pretty simple : this mro thing is not really a function
that will be used by the typical user of the poset class, so why don't we
just hide it ? It's internal stuff, so why don't we keep it internal ?
And I don't insist on anything. I just wondered about it, as it did not
seem right. What do you think ?
Nathann
--
Ticket URL: <http://trac.sagemath.org/ticket/13250#comment:9>
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.
