On Wed, 30 Sep 2009 11:22:20 -0700 (PDT)
kcrisman <kcris...@gmail.com> wrote:

> Is there any possibility of Pynac becoming part of the standard Sage
> mercurial repo?  In the sense that one would have immediate access to
> changes to it via hg_sage, etc.  Maybe that's not kosher, since those
> C ++ files aren't generated by Cython.  But it would make it a lot
> easier to do, and presumably others who need symbolics would like to
> have an easier way to talk about them, since changes in Pynac can have
> big influence on Sage.

Importing the pynac source into the Sage mercurial repository would be
similar to adding the eclib, ratpoints, or all the other "libraries"
Sage depends on.

The main reason that changes in pynac are necessary to fix some bugs in
Sage symbolics is that we don't have a clear interface between Sage and
pynac. This is partly caused by the fact that we switched over to using
pynac for the symbolics backend very quickly without sorting out some
of these issues. I'm quite sure that after resolving a few remaining
issues (like this symbolic functions interface) we won't have to touch
pynac so much.

Besides, it's not that hard to get to the pynac code. Just do

./sage -f -s pynac-0.1.9-p0.spkg
cd spkg/build/pynac-0.1.9.p0/src

If you make any changes, be sure to have a sage shell with

./sage -sh

then go to the directory above and do 

make install


> However, that might be a pretty difficult thing to do - just throwing
> it out there.  Thanks for all the work on it, as usual!  Now if I only
> understood enough to help Nils get library access to ECL/Maxima, we'd
> really be in business...

I really wish there was more work to make that interface usable.


Thanks.

Burcin

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to