#19041: Better description of docstrings in the developer guide
-------------------------------------+-------------------------------------
Reporter: vdelecroix | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.9
Component: documentation | Resolution:
Keywords: | Merged in:
Authors: Vincent | Reviewers: Nathann Cohen
Delecroix, Jori Mäntysalo | Work issues:
Report Upstream: N/A | Commit:
Branch: | d01d36d74b80e44b6676c82b5ae02247e3200e30
u/jmantysalo/19041 | Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by ncohen):
> This is not that easy; I can see plus-points for both sides: Using such
a flag means to have only *one* function for the desired functionality,
which is usually a good thing. On the other hand, getting different a
output type depending the input is sometimes not seen as good practice.
If you want to start changing these things, please add me in Cc of the
tickets. I do not consider that such "variable" outputs are a problem,
given that the output format is decided by the input: you get what you
asked for, exactly as if you had called a different function.
Nathann
--
Ticket URL: <http://trac.sagemath.org/ticket/19041#comment:26>
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.
