#18121: Patch Cython with PyTypeObject members
-------------------------------------+-------------------------------------
Reporter: jdemeyer | Owner:
Type: enhancement | Status: closed
Priority: major | Milestone: sage-6.7
Component: packages: | Resolution: fixed
standard | Merged in:
Keywords: sd66 | Reviewers: Vincent Delecroix,
Authors: Jeroen Demeyer | Nils Bruin
Report Upstream: Fixed upstream, | Work issues:
but not in a stable release. | Commit:
Branch: | Stopgaps:
58c17fbe84b31e534be250907717c52b8827e1d8|
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by leif):
Replying to [comment:36 vbraun]:
> this ticket was opened before 6.7
So what? Besides that `vbraun_spam` appears to be on holidays since a
while, certainly 6.6 got released before this ticket got closed. (And
it's based on 6.7.beta2.)
If someone sees a closed milestone on a (closed) ticket, the first guess
is that it'd been merged into that release.
I'm certainly not the only one not wanting having to read the ticket
history and/or to look up the parent(s) of the commit to find out whether
that's true or not.
Especially "ordinary" Sage users simply won't do that, e.g. if they want
to find out whether a bug has already been fixed, and if so, in which
[stable] release.
--
Ticket URL: <http://trac.sagemath.org/ticket/18121#comment:37>
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.
