On Friday, October 24, 2014 11:04:23 AM UTC-4, Travis Scrimshaw wrote:
>
> I think the exact opposite should happen, that the test should be
> removed. This could lead to (somewhat) surprising different behaviors for
> doctests on (essentially) everyone else's version Sage.
>
Just to make sure. There are two distinct cases when running sage -t on a
file :
1. The file is a Sage library file.
2. The file is not a Sage library file. In this case, the code of the file
is first imported before running tests.
One can actually avoid importing anything from the file with (see sage -t
--help):
--force_lib, --force-lib
assume all files are Sage library files, regardless
of
location, ie don't import anything from the file
tested
My question concerns only the case 2. When the file is not a Sage library
file, should we import init.sage before running the test?
....or maybe it could simply become a new option for sage -t...
Sébastien
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
