On Tue, Apr 15, 2008 at 9:11 AM, Jason Bandlow <[EMAIL PROTECTED]> wrote: > > Hello all, > > Regarding doctesting, I'd like to work with the following setup: > 1. Create a file work.sage (or work.py) somewhere in my home directory. > 2. Start a notebook session, and attach work.sage. > 3. Use the notebook for generating and staring at data, while using a > text editor to modify my code. > 4. Periodically run: $ sage -t work.sage to make sure that I > haven't completely fouled things up. > > Step 4 seems not to work (on Sage 2.11 on Ubuntu). For example, > I created the following file, foo.py, in my ~/.sage directory:
As a workaround do not put foo.py in .sage; put it in *any* other directory that does not start with a dot. Then everything should work fine. -- William > > def foo(x): > r""" > Shows how doctests don't work. > > EXAMPLES: > sage: 2+2 > 5 > sage: foo(3) > 4 > """ > print(x) > > And then > $ sage -t --verbose ~/.sage/foo.py > > ---------------------------------------------------------------------- > All tests passed! > Total time for all tests: 0.0 seconds > > $ sage -coverage ~/.sage/foo.py > ---------------------------------------------------------------------- > foo.py > SCORE foo.py: 100% (1 of 1) > ---------------------------------------------------------------------- > > > Can someone explain to me what's going on here? > > Thanks, > Jason > > > > > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
