On 27 Mai, 16:59, kcrisman <kcris...@gmail.com> wrote: > On May 27, 10:32 am, leif <not.rea...@online.de> wrote: > > > > > On 27 Mai, 02:34, William Stein <wst...@gmail.com> wrote: > > > > On Wed, May 26, 2010 at 5:31 PM, kcrisman <kcris...@gmail.com> wrote: > > > > >> > Not without having someone over your shoulder, which is why I still > > > >> > don't/can't use them. (Maybe Rob and Jason will finally teach me > > > >> > when > > > >> > they visit in June!). > > > Go for it! I wrote hg_sage in a big hurry, and had always expected > > > *YOU* were going to come along and greatly improve it, e.g., filling > > > out all the capabilities, adding full support for queues, etc. > > > Should there be a layer of abstraction from Mercurial for beginners, > > such as e.g. > > > apply_patch(...), show_changes(), create_patch(), export_patch(...) > > etc.? > > > (The functions could then also explain what they do, if verbose=True.) > > Well, we already basically have this in > > sage: hg_sage.import_patch?
This is still very closely oriented at Mercurial (both function names and syntax/usage; of course "hg_*" simplifies look-up by tab- completion). > but it would be worth improving the documentation here (another big > project). I don't know whether we want global functions for this or > not. import sage.beginner > Another problem is you can't really run doctests, but maybe it could > at include "#not tested" style examples. Another thing to add to my > list. print kcrisman.todo_list.len() # or .keys().len()? ;-) -Leif -- 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
