#9901: update pynac to 0.2.1
-----------------------------+----------------------------------------------
Reporter: burcin | Owner: burcin
Type: defect | Status: needs_review
Priority: major | Milestone: sage-4.6
Component: symbolics | Keywords: pynac
Author: Burcin Erocal | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------------+----------------------------------------------
Comment(by kcrisman):
Most of the changesets are pretty obviously related to the tickets in
question, and I'll put comments there. Here are a few things which I will
put here for archiving which came up in discussion, because a few
changesets in Pynac are nonobvious.
{{{
> As far as Pynac is concerned:
>
> "Do not generate function.{h,cpp} automatically." How do I check
> this? What is the reasoning for this? How do you test this in the
> Sage library (say, for 13 arguments), as it probably should be? Why
> do you keep it for (say) 3, but not 4?
You can't check this in the Sage library. The auto generated calls were
something we inherited from GiNaC as a convenience for programming in
C++. Since we use Python, which uses a function call mechanism very
similar to the vector arguments case GiNaC supports, there is no reason
to keep the auto generated functions.
I kept the calls up to 3, since functions implemented in GiNaC use at
least up to 2. I don't know if there is anything which needs 3.
> Are some of these things items you would want to report upstream? I
> am thinking of the conjugate handling, for instance, or the unsigned
> infinity. Maybe they come from upstream?
> Changeset 172 - what is that all about?
It just deletes some files from the mercurial repository. They are
generated by autoconf. William just imported everything in the GiNaC
distribution tarball when he started working on pynac. This is just
cleaning up some of that cruft.
}}}
Incidentally, we also note that the conjugate handling change came from
upstream.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9901#comment:3>
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.