Add an option to hg_sage that allows one to setup a fake repo in a tmp directory... Then test everything on that. Add support for queues while you're there. :-) On Tuesday, August 3, 2010, kcrisman <[email protected]> wrote: > The file misc/hg.py needs a lot of doctests to bring things up to > speed for Sage 5.0. I think this would be a great way to learn about > the internals of this, and would like to try. > > But unfortunately I have no idea whether it is possible to actually > test some of these things, since running some of them would > immediately break if someone made changes, and how the heck would one > doctest > > hg commit > > if there is nothing changed? And so forth. Is a revision control > system something one can doctest for in our framework? Maybe it is > pretty obvious and I am just missing something, but for instance > testing > > sage: hg_sage.rollback() > > seems like a test that could only work once, and might even be > dangerous. > > Thanks for any ideas, > > - kcrisman > > -- > To post to this group, send an email to [email protected] > To unsubscribe from this group, send an email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/sage-devel > URL: http://www.sagemath.org >
-- William Stein Professor of Mathematics University of Washington http://wstein.org -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
