#9880: Segfault in PyNaC 0.2.0.p4
-------------------------+--------------------------------------------------
Reporter: jpflori | Owner: burcin
Type: defect | Status: needs_work
Priority: major | Milestone: sage-4.7
Component: symbolics | Keywords: pynac
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies:
-------------------------+--------------------------------------------------
Comment(by burcin):
I don't want to delay this any further, but if this is merged all patches
touching anything symbolic will need to be rebased. I suggest we try to
review and merge any feasible symbolics tickets for the next release. Then
this gets merged for 4.8 with big warnings, since users would also need to
change doctests in any private code they might have.
I can actually spare time for such an effort now. I will see what I can do
with the needs review/work tickets on trac starting tomorrow.
BTW, we should also include Volker's test script. Perhaps as a part of
`sage/symbolics/random_tests.py`.
Jean-Pierre: Yes, by operand access I mean the `.operands()` and the
recent `.op` from #9989.
Making a pynac release is just a matter of editing `configure.ac`, setting
the version number according to the comments there and running
`autoreconf` afterwards. I am not sure any more if the next pynac release
should contain this. This can be pynac 0.3.0, and I will put in the
patches in my queue corresponding to some of the tickets waiting on trac
for 0.2.2.
Note that I imported the pynac-0.2.1 repository into bitbucket:
https://bitbucket.org/burcin/pynac
I hope to use the facilities there to streamline the development process.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9880#comment:40>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
