Re: [sage-devel] Modular forms slowdown

2013-01-08 Thread Jeroen Demeyer
On 2013-01-07 23:43, Volker Braun wrote: > But the command is mostly linear algebra over QQ. Its possible that the > old GCC does something very stupid, but I doubt that you can speed up > integer computations by a factor of 5x just by optimizing code paths. So > it pretty much must be the blas ins

Re: [sage-devel] Re: Removing startup.py test

2013-01-08 Thread Robert Bradshaw
On Mon, Jan 7, 2013 at 11:32 PM, Jeroen Demeyer wrote: > On 2013-01-07 23:54, Robert Bradshaw wrote: >> I consider startup time to be one of our biggest bugs... > I suggest to start with the notebook. Merging the flask notebook added > about 0.5s to the startup time IIRC. Which is silly since th

Re: [sage-devel] Modular forms slowdown

2013-01-08 Thread Jeroen Demeyer
On 2013-01-08 09:11, Jeroen Demeyer wrote: > On 2013-01-07 23:43, Volker Braun wrote: >> But the command is mostly linear algebra over QQ. Its possible that the >> old GCC does something very stupid, but I doubt that you can speed up >> integer computations by a factor of 5x just by optimizing code

[sage-devel] Add a few # long time (#13924) needs review

2013-01-08 Thread Jeroen Demeyer
All this patch does is add # long time in a few places. Please review: http://trac.sagemath.org/sage_trac/ticket/13924 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscrib

Re: [sage-devel] Modular forms slowdown

2013-01-08 Thread Jeroen Demeyer
On 2013-01-07 20:50, Jeroen Demeyer wrote: > On 2013-01-07 12:24, Jeroen Demeyer wrote: >> I am running the command >> >> sage: time B = >> ModularFormsRing(Gamma0(3)).modular_forms_of_weight(80).cuspidal_submodule().q_expansion_basis(prec=30) >> >> sage-5.4: 17.94 s >> sage-5.5: 56.28 s > > I can

Re: [sage-devel] Re: Removing startup.py test

2013-01-08 Thread Jeroen Demeyer
On 2013-01-07 23:49, William Stein wrote: > I'm fine with removing it, since it doesn't do any good anyways. OK, please review http://trac.sagemath.org/sage_trac/ticket/13927 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, s

[sage-devel] Re: Simple change from a staleld ticket

2013-01-08 Thread Simon King
Hi Nils, On 2013-01-08, Nils Bruin wrote: > which caused much of the problems observed on #13400. It was found on > that ticket that the routine can simply be deleted, because there's a > better implementation somewhere further up the inheritance tree. Since > #13400 doesn't seem to be going anyw

[sage-devel] Fix sig_block() doctest (#13748) needs review

2013-01-08 Thread Jeroen Demeyer
Apparently, it is illegal to exit a try: block when sig_on() is in effect. But a doctest in sage/tests/interrupt.pyx does this and should be fixed. This blocks the new doctesting framework. So please review: http://trac.sagemath.org/sage_trac/ticket/13748 Thanks, Jeroen. -- You received this me

Re: [sage-devel] Re: Removing startup.py test

2013-01-08 Thread Volker Braun
First of all, is there a problem? Sage starts in less than a second on my desktop if caches are warm. I didn't write the sage-forker, but I did write a module importer that would get rid of all the failed open() attempts. Python does many unnecessary filesystem operations when starting up. E.g

Re: [sage-devel] Re: Removing startup.py test

2013-01-08 Thread Jeroen Demeyer
On 2013-01-08 12:28, Volker Braun wrote: > E.g. when you import > foo then foo.{py, pyc} must be searched in the whole Python path. Not to mention foo.so and the directory foo/ -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group,

[sage-devel] Sage, Python packages, and .local

2013-01-08 Thread kcrisman
See http://ask.sagemath.org/question/2145/compiling-sage-55-matplot-lib-fails-to-find-numpy Is this a bug or a feature? I'm assuming the poster "Dr. Whom" is correct. In any case, this behavior should either be documented or corrected, depending on the situation. Sage's built-in version of Py

Re: [sage-devel] Sage, Python packages, and .local

2013-01-08 Thread Jeroen Demeyer
On 2013-01-08 16:35, kcrisman wrote: > See > http://ask.sagemath.org/question/2145/compiling-sage-55-matplot-lib-fails-to-find-numpy > Is this a bug or a feature? Feature: http://www.python.org/dev/peps/pep-0370/ -- You received this message because you are subscribed to the Google Groups "sag

Re: [sage-devel] Sage, Python packages, and .local

2013-01-08 Thread Jeroen Demeyer
Note in particular: "The user site directory is added before the system site directories[...]" So yes, it's a feature. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscri

Re: [sage-devel] Re: Why does - (x > 100) return -x > -100 ?

2013-01-08 Thread Andrey Novoseltsev
On Monday, 7 January 2013 14:04:36 UTC-7, Benjamin Jones wrote: > > On Mon, Jan 7, 2013 at 10:53 AM, Keshav Kini > > > wrote: > > Benjamin Jones > writes: > > > >> On Mon, Dec 17, 2012 at 9:32 PM, P Purkayastha > >> > > > >> wrote: > >> > >> On 12/18/2012 10:10 AM, Benjamin Jones wrote

[sage-devel] Re: Simple change from a staleld ticket

2013-01-08 Thread Nils Bruin
On Jan 8, 2:12 am, Simon King wrote: > I don't know what a "rider patch" is, but go ahead. Briefly looking at > the discussion on #13400, it seems that this ticket should be split in > several independent small tickets anyway. I just figured it could be included in a somewhat related ticket, but

[sage-devel] Re: Problem with sage -tp and SAGE_ROOT = $HOME/.Sage/

2013-01-08 Thread leif
Nathann Cohen wrote: > > Helloo everybody !! > > I finally found out where my bug from [1] was coming from ! > > It seems to come from the fact that I installed Sage in the directory > $HOME/.Sage/. And Sage does not like that. Actually, it refuses to test any > file whose path contains "/.

Re: [sage-devel] Re: Why does - (x > 100) return -x > -100 ?

2013-01-08 Thread Julien Puydt
Le 08/01/2013 17:50, Andrey Novoseltsev a écrit : So, what should x*(y > 0) do, raise a NotImplementedError? And x*(y == 0)? I guess we just special case inequalities. I hit my students with a cluebat (though only metaphorically... [giant sigh]) when they multiply an inequality without

Re: [sage-devel] Re: Why does - (x > 100) return -x > -100 ?

2013-01-08 Thread Volker Braun
On Tuesday, January 8, 2013 5:59:09 PM UTC, Snark wrote: > For the equality, there's no problem. > Is it? 1 == 0 (false) 1*0 == 0*0 multiply both sides 0 == 0 (true) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to thi

Re: [sage-devel] Re: Why does - (x > 100) return -x > -100 ?

2013-01-08 Thread Julien Puydt
Le 08/01/2013 19:25, Volker Braun a écrit : On Tuesday, January 8, 2013 5:59:09 PM UTC, Snark wrote: For the equality, there's no problem. Is it? 1 == 0 (false) 1*0 == 0*0 multiply both sides 0 == 0 (true) I don't see it as a problem, as "false implies true" is true. The on

[sage-devel] Re: Removing startup.py test

2013-01-08 Thread Nils Bruin
On Jan 8, 3:28 am, Volker Braun wrote: > The notebook stuff hurts us twice in import times: First, many modules have > their path added to sys.path making it longer. Second, the notebook stuff > is actually imported in a plain commandline Sage session. And the modules > are pretty slow, for exampl

[sage-devel] Evolve extension in hg: almost ready for use

2013-01-08 Thread Jordi Gutiérrez Hermoso
Evolve is an hg extension that is rapidly converging to a very nice replacement for MQ: http://hg-lab.logilab.org/doc/mutable-history/html/evolve-faq.html http://hg-lab.logilab.org/doc/mutable-history/html/from-mq.html The idea of evolve, sort of, is to be able to collaboratively amend hi