To me it is not a problem of doc but a problem of code. The issue is that we have 99% of the poset functions in the poset/ folder, and a couple of them in the category/ folder. If we move everything to posets, there's no problem. I don't see any advantage in having poset code in a file that is meant to implement the category of posets.
Nathann On Monday, June 8, 2015 at 4:27:29 PM UTC+2, Jori Mäntysalo wrote: > > There is some discussion at http://trac.sagemath.org/ticket/18534 . Maybe > this could be a topic in this sage-devel list also. > > For now there is no list of "what can I do with these posets" -functions. > That's because we have, for example, is_connected() on > .../combinat/posets/posets.py and is_selfdual() on categories. And > basically this is a question of viewpoint for documentation. Should we see > it as documenting code, or as documenting functions for the user? > > -- > 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
