Re: [sage-devel] Re: cached_function: a filter to only cache some inputs ?

2014-06-07 Thread kcrisman
> > But right now, what Nathann is trying to do is rather orthogonal to > these questions. If somebody comes with a nice class that *does not* > slow down his construction code, everybody will be happy. Sage is open > to contributions and not only to critics ;-P > > Thanks for having a look

Re: [sage-devel] Re: Recommendations for a new Parent/Element pair

2014-06-07 Thread R. Andrew Ohana
Yeah, I also found some morphisms in the polynomial ring code, but like the QQ <-> ZZ code, it seemed dated (and hence might not follow recommended practices). As for sage.algebras.*, I didn't really see anything other than Boolean return values. On Fri, Jun 6, 2014 at 9:21 AM, Vincent Delecroix

[sage-devel] Re: reduce compilation times during development

2014-06-07 Thread Volker Braun
On Saturday, June 7, 2014 2:50:41 PM UTC+1, leif wrote: > > Is ccache agnostic to the comment on the first line of each > Cython-generated C/C++ file? > Jein ;-) Leads to a direct mode cache miss. But the slightly slower preprocessor mode will ignore comments and hence match. -- You receiv

[sage-devel] Re: reduce compilation times during development

2014-06-07 Thread leif
Volker Braun wrote: There are some global dependencies, most notably setup.py. So if you change that then every *.pyx file is re-cythonized, and hence gcc called on every one of them. If there was no change to the Cython output then gcc should answer everything from ccache, so it would still be f

[sage-devel] Re: Logs for aleph.sagemath.org

2014-06-07 Thread leif
Ivan Andrus wrote: On Jun 6, 2014, at 7:11 AM, Jason Grout wrote: On 6/5/14, 2:33, Ivan Andrus wrote: Are there logs (and if so where are they?) for aleph.sagemath.org? I'm trying to figure out what sorts of things the iOS app is used for. Yes, there are logs. Right now, we log remote i

[sage-devel] Re: Inconsistency in element class. Is it a bug or intended?

2014-06-07 Thread Volker Braun
This is a bug, elements should always be of the type Parent.element_class. The element constructor right now is def _element_constructor_(self, x): """ TESTS:: sage: B = BraidGroup(4) sage: B([1, 2, 3]) # indirect doctest s0*s1*s2

[sage-devel] Re: Build error in Sage-6.2: pynac-0.3.2

2014-06-07 Thread leif
Vincent Delecroix wrote: Have a look at the commands chown: change the owner/group chmod: change permissions What you have to do is to make /opt/sage-6.2 writable by you, not the whole /opt. The simplest way, assuming that your username is alasdair, is to change the owner of everything in /o

[sage-devel] Inconsistency in element class. Is it a bug or intended?

2014-06-07 Thread mmarco
I have found the following behaviour: {{{ sage: B=BraidGroup(4) sage: b=B([1,2,3]) sage: type(b) sage: type(b*b) }}} Both b and b*b have the same parent, but they belong to different classes. I guess that the fact that they are constructed by different methods (BraidGroup.__call__ vs, BraidGr

[sage-devel] Set_object_enumerated

2014-06-07 Thread Vincent Delecroix
Hi, I am refactoring subset / subword at #10534. The "elements" are right now of type Set_object_enumerated. But I really do not like it since: sage: from sage.sets.set import Set_object_enumerated sage: Set_object_enumerated((Set(()), Set((2, {{2}, {}} sage: Set_object_enumerated((Set(()), S

[sage-devel] Re: reduce compilation times during development

2014-06-07 Thread Volker Braun
There are some global dependencies, most notably setup.py. So if you change that then every *.pyx file is re-cythonized, and hence gcc called on every one of them. If there was no change to the Cython output then gcc should answer everything from ccache, so it would still be fast. Of course you

Re: [sage-devel] Re: cached_function: a filter to only cache some inputs ?

2014-06-07 Thread Volker Braun
There are many places where Sage provides a nice frontend class while the actual computation is implemented differently. Of course you could just use libsingular directly to compute with polynomial, right? ;-) In particular, it would be perfectly reasonable to have a "frontend" class that acts

Re: [sage-devel] Build error in Sage-6.2: pynac-0.3.2

2014-06-07 Thread Vincent Delecroix
Have a look at the commands chown: change the owner/group chmod: change permissions What you have to do is to make /opt/sage-6.2 writable by you, not the whole /opt. The simplest way, assuming that your username is alasdair, is to change the owner of everything in /opt/sage-6.2 with sudo chown

Re: [sage-devel] Build error in Sage-6.2: pynac-0.3.2

2014-06-07 Thread Alasdair
Thanks for that - I compiled it as root, so that it could write to the directory /opt/sage-6.2. There should have been no permission problems. (In essence, I did what I've always done: opened up a login shell as root, and installed sage in the directory /opt/sage-x.y. However! I've just di

Re: [sage-devel] Re: cached_function: a filter to only cache some inputs ?

2014-06-07 Thread Vincent Delecroix
> Actually, I was kind of surprised that they were just lists of lists when I > was looking at the code. Surely one wants more structure than that, or > don't they have more structure? This is exactly the kind of thing we are > just talking about with the game theory code - we want a class becaus

[sage-devel] Re: reduce compilation times during development

2014-06-07 Thread Ralf Stephan
On Monday, May 12, 2014 11:36:20 AM UTC+2, P Purkayastha wrote: > > ... It shouldn't have upgraded anything, but it still decided to compile a > bunch of packages anyway. > I have witnessed the same thing recently. Someone with knowledge of the code please correct me. I think what is probably ha