Hi Mariah, On 16 Sep., 15:29, Minh Nguyen <nguyenmi...@gmail.com> wrote: [...] > Do you mean producing a proper patch file using Mercurial? If yes, > then you can use the Mercurial that's shipped with Sage like so. From > SAGE_ROOT, you can do something along the lines of the following > terminal session: > > [mv...@sage sage-4.1.1-sage.math]$ ./sage > ---------------------------------------------------------------------- > | Sage Version 4.1.1, Release Date: 2009-08-14 | > | Type notebook() for the GUI, and license() for information. | > ---------------------------------------------------------------------- > sage: !bash > [mv...@sage sage-4.1.1-sage.math]$ cd devel/sage-main/ > [mv...@sage sage-main]$ emacs sage/misc/misc.py > > # or use your favourite editor to make changes to that misc.py file
There is also a different way in Sage: For example, sage: from sage.misc.misc import xsrange sage: edit(xsrange,'vi') would open your favourite editor (vi, of course...) exactly where xsrange is defined. I find this a very clever and helpful tool, so, cudos to whoever implemented it! Then you can edit it, and save. > [mv...@sage sage-main]$ hg ci # now check in your changes > No username found, using 'mv...@sage.math.washington.edu' instead > [mv...@sage sage-main]$ hg export tip > ~/mypatch.patch > [mv...@sage sage-main]$ exit > exit > sage: exit This can in principle also be done differently, whithout going to a shell: Inside a sage session, there is "hg_sage", that provides you with methods such as hg_sage.log(), hg_sage.commit(), hg_sage.export (nb,patchname). Just do "hg_sage?" for getting more information. Best regards, Simon --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
