Re: [sage-devel] Should sage-bdist determine version number of Sage?

2014-08-11 Thread kcrisman
Sorry to resurrect this - apparently this happened, quite silently and backwards-incompatibly, in http://trac.sagemath.org/ticket/15527 . -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails fro

[sage-devel] Sage Days at PyCon 2015

2014-08-11 Thread Viviane Pons
Hi everyone, I've just written to the PyCon organizing team about making SageDays as a satelite even for next year conference (April 2015). The idea would be to organize the Sage Days during the sprint days of the PyCon conference. This is not done yet but I'm very confident it's going to happen!

Re: [sage-devel] You should rebuild using libgmp >= 5

2014-08-11 Thread kcrisman
> > > That is reassuring! It would be nice if we could prevent the warning > appearing at all, as it clearly worries people. > > +1 I see this all the time too, though I assumed it was fine. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

[sage-devel] patchbot/build issues ?

2014-08-11 Thread Jakob Kroeker
Hello, when I try to run *patchbot* on machine 'A' I observe several errors, e.g. Getting ticket list... fatal: Invalid revision range 389fbf0cd408302c14635d7979f39297c1f6a2b2..patchbot/base Resolving sage.math.washington.edu... 128.208.160.197 Connecting to sage.math.washington.edu

Re: [sage-devel] You should rebuild using libgmp >= 5

2014-08-11 Thread John Cremona
On 11 August 2014 13:05, Volker Braun wrote: > Pycrypto is not used to implement anything security-relevant. It is safe to > ignore the warning. That is reassuring! It would be nice if we could prevent the warning appearing at all, as it clearly worries people. John > > > > > On Monday, Augus

Re: [sage-devel] You should rebuild using libgmp >= 5

2014-08-11 Thread Volker Braun
Pycrypto is not used to implement anything security-relevant. It is safe to ignore the warning. On Monday, August 11, 2014 12:50:59 PM UTC+1, Daniel Krenn wrote: > > Am 2014-02-27 um 01:07 schrieb Andrey Novoseltsev: > > When I try to start a notebook from 6.1.1, I get > > > > sage-6.1.1/lo

Re: [sage-devel] You should rebuild using libgmp >= 5

2014-08-11 Thread Daniel Krenn
Am 2014-02-27 um 01:07 schrieb Andrey Novoseltsev: > When I try to start a notebook from 6.1.1, I get > > sage-6.1.1/local/lib/python2.7/site-packages/Crypto/Util/number.py:57: > PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild using > libgmp >= 5 to avoid timing attack vulnerabili

[sage-devel] Re: Doctesting nostests

2014-08-11 Thread Volker Braun
How about an optional argument long=True which you can then set to False in the doctest. On Monday, August 11, 2014 8:45:51 AM UTC+1, Martin Raum wrote: > > Hello, > > I'm asking for advice here. I have some modular forms code, and since I'm > into test driven development when writing Python, i

Re: [sage-devel] Category framework strangeness

2014-08-11 Thread John Cremona
On 10 August 2014 22:49, Nicolas M. Thiery wrote: > On Thu, Jul 17, 2014 at 05:37:48PM +0200, Vincent Delecroix wrote: >> Whaou. I guess it means: Category of (associative additive) >> (commutative additive) (associative additive) unital distributive >> magmas and additive magmas. But definitely,

[sage-devel] Doctesting nostests

2014-08-11 Thread Martin Raum
Hello, I'm asking for advice here. I have some modular forms code, and since I'm into test driven development when writing Python, it comes with a lot of tests run by nosetest. I would like to include this into Sage as part of my code. Question 1: Where to put this? There are two obvious ch

Re: [sage-devel] On scientific computing, Python and Julia

2014-08-11 Thread Ralf Stephan
I would like to thank Eric Massop for his excellent and enlightening posts. On Saturday, August 9, 2014 11:58:20 PM UTC+2, Erik Massop wrote: > > On Wed, 6 Aug 2014 19:00:22 -0700 (PDT) > rjf > wrote: > > > On Tuesday, August 5, 2014 7:59:00 PM UTC-7, Robert Bradshaw wrote: > > > > > > On Tue,