On Mon, 25 Aug 2014, Travis Scrimshaw wrote:
IIRC most of the doc is in the header of some module... just use view(P,
tightpage=True), it uses dot2tex if you install the optional spkg (with
sage -i dot2tex). IMO the output is much prettier.
For example view(Poset( ([1,2,3,4,5], [[1,2],[1,3],[3,4],[2,5],[4,5]]) ),
tightpage=True) does nothing.
But how come categories to this picture?
As I stated, they can act like ABC's (abstract base classes), but can be
set at runtime based on inputs (see MatrixSpace(R, m, n) with m = n and
with m != n). Here's also a nice tutorial on the subject. Although they
carry more information with them which is used for the morphisms.
OK, maybe I understood a little of that.
But then going back to tode. For example posets.py has
def has_top(self):
return self._hasse_diagram.has_top()
and documentation and two examples. hasse_diagrams.py contains
def has_top(self):
if not self.top() is None: return True
return False
and almost same documentation and exactly same examples. Why isn't that
code put directly to posets.py?
--
Jori Mäntysalo
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
