#16998: Documentation conflict on is_graded()
-------------------------------------+-------------------------------------
Reporter: jmantysalo | Owner:
Type: defect | Status: needs_review
Priority: minor | Milestone: sage-6.4
Component: combinatorics | Resolution:
Keywords: | Merged in:
Authors: Jori Mäntysalo | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/jmantysalo/documentation_conflict_on_is_graded__|
d66dffdbb4abbc684fcc771c5c38886a3cbc5849
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by jmantysalo):
Replying to [comment:8 stumpc5]:
> Why did you decide to deprecate it rather than checking whether the
Hasse diagram is graded?
What if somebody has really used `is_graded()` directly on hasse diagram,
expecting it to say `True` if the hasse diagram is ranked? Of course
nobody should do that, but instead use poset.
And on sage-devel list we discuss about moving code away from
`hasse_diagram.py`.
--
Ticket URL: <http://trac.sagemath.org/ticket/16998#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/d/optout.
