#4633: [with patch, needs review] fix additional "Fortran-style" names and a
coercion
------------------------+---------------------------------------------------
Reporter: bpage | Owner: was
Type: defect | Status: new
Priority: major | Milestone: sage-3.2.2
Component: interfaces | Resolution:
Keywords: axiom |
------------------------+---------------------------------------------------
Comment (by bpage):
Replying to [comment:7 tjlahey]:
> Is there a specific procedure for installing (and testing) these kinds
of patches? That is, how do I get Sage to know that the code has been
updated? This kind of thing would be nice on a wiki page for new
developers. Or have I just missed it?
This is what I do:
0. Pretest, e.g. try: axiom(1/log(x)).sage()
{{{
NotImplementedError
}}}
1. Click on the link to that patch: "trac_4633.patch"
2. Click on the link to "original format"
3. Save the patch file somewhere, e.g. ~/trac_4633.patch
4. cd sage*/devel/sage-main
5. apply the patch: patch -p1 < ~/trac_4633.patch
6. re-build sage: sage -br
7. test, e.g. try: axiom(1/log(x)).sage()
{{{
1/log(x)
}}}
I guess that in a more complete patch I should have added some tests like
this to the doc tests. This just seemed too simple.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/4633#comment:8>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
