[sage-devel] spkgs assumed for doctesting but not default installed

2016-06-29 Thread Johan S . H . Rosenkilde
Hi sage-devel Today I made a fresh clone of the develop branch, ran "make", and then tried to run "./sage -t". To my surprise, this didn't work at all! First off, the doctest framework wouldn't even run, since sympy wasn't installed. After doing "./sage -pip install sympy", I could now actually p

[sage-devel] Deprecation warnings are no longer printed?!

2016-06-29 Thread Johan S . H . Rosenkilde
sage: import warnings sage: warnings.filterwarnings('always',".*", DeprecationWarning) sage: deprecation(3,"m") Hi sage-devel, On my Sage installation, as well as on David Lucas' (having different Linux distros), the following *does not* print the expected deprecation warning in the Sage shell or

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

2016-06-23 Thread Johan S . H . Rosenkilde
Seems like a similar patch needs to be applied to git_trac/digest_transport.py when your system defaults to Python 3. Best, Johan Volker Braun writes: > Thats because of https, you need to do the analog change that I just did on > the git-trac script: > > diff --git a/git_trac/digest_transpor

Re: [sage-devel] more tests in sage (not doctests)

2016-06-22 Thread Johan S . H . Rosenkilde
> It's a little dangerous, our doctest framework uses the XKCD random > number generator. There's prior work by S. Adams: http://dilbert.com/strip/2001-10-25 Best, Johan -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this gr

Re: [sage-devel] more tests in sage (not doctests)

2016-06-22 Thread Johan S . H . Rosenkilde
Big +1. There's the sage/tests folder which seems to be a place where certain developers who really couldn't help themselves put some additional tests. But it doesn't go near as far as what you're proposing. However, there's obvious issues wrt. ensuring that such tests gets written once in a whil

<    1   2