On Saturday, April 7, 2018 at 11:27:35 AM UTC+2, Simon King wrote:
>
> Hi Thierry, 
>
> On 2018-04-07, Thierry <sage-goo...@lma.metelu.net <javascript:>> wrote: 
> > What is wrong with adding the following to the tests that try to connect 
> > to the internet, whether they absolutely depend on it or not ? 
> > 
> >         # optional -- internet 
>
> It would mean that these tests wouldn't be executed at all without 
> internet, and that's not what I want. 
>
> > Also, i am not sure that: 
> > 
> > - people are happy that someone somehere is aware each time they are 
> >   doctesting Sage. 
> > - servers offering online databases are happy to waste CPU and bandwidth 
> >   for Sage doctesting. 
>
> Exactly. And that's why I'd be in favour of blocking internet access 
> during tests. 
>
> Meanwhile I was reminded by Jeroen that my memory was wrong: Internet 
> access is not blocked during doctests, but it *is* blocked during 
> package installation. 
>
> That brings back my other question: Is there an easy way to test whether 
> the Sage doctest framework is running? I.e., a function have_doctests() 
> that returns True when called in a doctest and returns False when run 
> interactively? 
>

You know, VW has vast experience with designing this sort of "tests" ;-)
 

>
> Best regards, 
> Simon 
>
>

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to