#18534: Posets: Adding function from categories to index of functions
-------------------------------------+-------------------------------------
Reporter: jmantysalo | Owner:
Type: enhancement | Status: needs_review
Priority: minor | Milestone: sage-6.8
Component: documentation | Resolution:
Keywords: | Merged in:
Authors: Jori Mäntysalo | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/jmantysalo/posets__adding_function_from_categories_to_index_of_functions|
b31c216bae73e63b9066778e2a3d569536ca91d2
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by ncohen):
> I would say "reject" to leaving things as they are. This patch is my
suggestion one. Suggestion two is to add index to category of posets, add
index to category of finite posets, and link them at the beginning of
index of finite posets. Suggestion three is to make a new page that
contains index of poset functions and a short introduction to posets in
Sage. All these suggestions assumes that the code itself will not be
refactored.
Move the two functions from categories to posets.py and the problem is
solved. I don't see the added value of having those two lone functions in
another file, where nobody will find them. Move them to `posets.py` and
they can obviously be added to the doc.
> (You may mean that I should stop doing tickets like #18925. If that is
the case, I must say that it is hard. To get unified interface it is
needed to sometimes go throught a bigger part of Sage. OTOH if I make a
big but simple patch of doctrings, it will take a year to write, will
needs rebasing ten times, and may never get positive_review.)
We could start getting rid of those big index, and of the duplication of
[1) the description of the function that follows the name of the function
in the index 2) the first line of the docstring of a function] by using
#18926.
Once this is done, the individual modifications do not need to be rebased
as often, for the parts of code that get modified are not all located in
the index: only the individual docstrings need be modified, and git has
less problems with that.
Nathann
--
Ticket URL: <http://trac.sagemath.org/ticket/18534#comment:13>
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.
