Hi,
I just talked to a student in my Sage course [1] who could not get the
network to work after tons of frustration.
There is an easy fix though. The problem was that the default network
interface got renamed by udev to eth6, but the file
/etc/network/interfaces only lists eth1-eth4.
So whoever
Hello,
I have done minor updates for the giac interface. (trac 10940)
I got the following bench with it:
On a: model name : Intel(R) Core(TM)2 Duo CPU E4700 @ 2.60GHz
with sage 4.6.2 compiled from sources and the giac spkg:
http://www-fourier.ujf-grenoble.fr/~parisse/giac/giac-0_9_1.spkg
(this spk
>>> I also noticed that the valgrind package is old; In particular it doesn't
>>> even compile on Fedora 14. But then its such a commonly-used tool that its
>>> already on every machine that is used for software development. The fact
>>> that nobody every complained about the outdated valgrind spkg
Hi there,
> I think, the question is (at least on the short run), how one can work
> around.
>
> Taking your example:
> class End(SageObject):
> def toto(self):
> return 1
> sage: c_long = long_mro(500)
> sage: obj_long = c_long()
> sage: obj_end = End()
> sage: timeit("obj_end.
Hi folks,
a quick summary of last week's Sage Days work from my perspective:
http://blog.fperez.org/2011/03/ipython-and-scientific-python-go-to.html
Thanks again to William for the workshop!
Cheers,
f
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from
Hi Nicolas,
On 30 Mrz., 09:44, Simon King wrote:
> When is that called? I provided a __init_extra__ for
> Rings.ParentMethods, but it is not called when I create R. =
> QQ['t'][], even though (with the patches from #9944 and #9138 at
> least) it belongs to a subcategory of the category of rings,
Hi Nicolas,
On 30 Mrz., 08:32, "Nicolas M. Thiery"
wrote:
> Another trick to try would be add in Modules.ParentMethods:
>
> def __init_extra__(self):
> self.basis_ring = self.base_ring
>
When is that called? I provided a __init_extra__ for
Rings.ParentMethods, but it is not c
Hi,
On 30 Mrz., 09:04, Simon King wrote:
> So, apparently it *was* thought of making these things cpdef!!
>
> Was there a reason to not make base and base_ring cpdef?
I tested, and found that cpdef'ing does not help (much):
With def:
sage: R. = QQ['t'][]
sage: timeit('R.base_ring')
625 loops, b
On 30 Mrz., 09:06, Simon King wrote:
> Would that work for objects that don't allow attribute assignment?
Well, there's always try-except, I suppose...
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...
On 30 Mrz., 08:32, "Nicolas M. Thiery"
wrote:
> Another trick to try would be add in Modules.ParentMethods:
>
> def __init_extra__(self):
> self.basis_ring = self.base_ring
Would that work for objects that don't allow attribute assignment?
--
To post to this group, send an e
Hi Nicolas,
On 30 Mrz., 08:32, "Nicolas M. Thiery"
wrote:
> On Wed, Mar 30, 2011 at 02:00:22AM -0400, David Roe wrote:
> > I think that base_ring and parent are cpdef'd methods (I don't want to
> > look it up at the moment).
>
> Not at this point apparently: category_object.pyx, line 479:
>
Based on my experience last October, teaching Sage at AIMS is highly
recommended. Feel free to email me off-list if you have questions.
Rob
On Mar 29, 11:55 am, Jan Groenewald wrote:
> Hi
>
> The deadline has been extended. The website will be updated shortly.
> We are still looking for a SAGE
12 matches
Mail list logo
