On Apr 17, 2:27 pm, "Nicolas M. Thiery" <nicolas.thi...@u-psud.fr>
wrote:

> But please please, let's do that smoothly without conflicting with all
> the current developments. To this end, I vote for sage -t to report
> tabs as warnings (not failures) for the moment.

I think this is a good idea, but might be a bit harder to implement.
That is, it's easy to print out a warning if there is a tab in a file
when the file is doctested, but if you doctest the whole Sage library,
printing out warnings at the end of all tests (separately, and in
addition to, failures) might be tricky.  But I think you have to have
some kind of summary at the end because it would be too easy to miss a
few warnings among the hundreds of files being tested.

I could be wrong about it being harder to implement...

> By the way, it would be nice to have sage -t also report as warnings:
>
>  - non ascii characters (unless the encoding is specified)
>  - trailing white spaces

Sounds good.

--
John

-- 
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

Reply via email to