#17847: Cython: embed signatures in docstrings
-------------------------------------+-------------------------------------
Reporter: jdemeyer | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: sage-6.6
Component: cython | Resolution:
Keywords: | Merged in:
Authors: Jeroen Demeyer, | Reviewers: Simon King
Simon King | Work issues:
Report Upstream: Fixed upstream, | Commit:
but not in a stable release. | 0fb0b34316949cdfbe5d369ebba2c9205f2a4014
Branch: | Stopgaps:
u/SimonKing/ticket/17847 |
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by SimonKing):
Replying to [comment:37 jdemeyer]:
> Replying to [comment:33 SimonKing]:
> > Why is that?
> Most likely, it is because `cython()` works completely independently
from `./sage -b` (this is certainly a bug, but outside the scope of this
ticket)
Why do you think it is outside the scope of this ticket? It is about
Cython embedding the signature into docstring, and I don't see why Cython
should distinguish `sage -b` from compilation of interactive code.
For sure, we can only use the embedded signature when it is ''uniformely''
embedded. Otherwise I don't see the point of embedding.
What about the additional blank line in a doc string? Do you think we
should simply insert it into the failing test in
`src/sage/sets/set_from_iterator.py`, or make it so that there is no
additional blankline?
--
Ticket URL: <http://trac.sagemath.org/ticket/17847#comment:39>
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.
