Hi Simon,
I thought of the proposal while fixing unpickling problem of the patch for
TermOrder objects for
http://trac.sagemath.org/sage_trac/ticket/11316
The situation I described originally is of course what I faced while fixing
the problem.
On 27 Mai, 18:10, Kwankyu Lee wrote:
> > How do
Hi Sage-Devel,
If you're a Sage developer seriously interested in improving Sage's
capabilities in "arithmetic dynamics" [1] (=number theory + dynamical
systems) email me, since there may be a conference I might be able to
get you invited to...
[1] http://en.wikipedia.org/wiki/Arithmetic_dynamics
On 05/28/2011 04:54 PM, Francois Bissey wrote:
> Hi,
>
> system:
> Linux 2.6.38-ARCH #1 SMP PREEMPT i686 Intel(R) Pentium(R) M processor
> 1600MHz GenuineIntel GNU/Linux
>
> with gcc 4.6.0
>
> Sage 4.7 fails to build. make exited with this error
> ---
> Hi,
>
> system:
> Linux 2.6.38-ARCH #1 SMP PREEMPT i686 Intel(R) Pentium(R) M processor
> 1600MHz GenuineIntel GNU/Linux
>
> with gcc 4.6.0
>
> Sage 4.7 fails to build. make exited with this error
> ---
> running build_ext
> building 'Crypto.PublicKey._fastm
Hi,
system:
Linux 2.6.38-ARCH #1 SMP PREEMPT i686 Intel(R) Pentium(R) M processor
1600MHz GenuineIntel GNU/Linux
with gcc 4.6.0
Sage 4.7 fails to build. make exited with this error
---
running build_ext
building 'Crypto.PublicKey._fastmath' extension
creati
On May 25, 2:22 pm, John Cremona wrote:
> If no-one else is more explicit I'll look for a reference tomorrow.
For the record, off-list John Cremona pointed me to "Fast Algorithms
for Linear Algebra mod N" by Storjohann and Mulders, where this is
called "stablization of p and q mod r" and the
Hi Simon,
> On 28 Mai, 18:12, Florent Hivert wrote:
> > Just to let you know, I tried the following work around:
> >
> > ...
> > but since A.toto.f.__name__ is still toto. It doesn't work. However the
> > following works (on unpatched sage-4.6.2):
> >
> > def change_name(fun, name):
> >
Hi Florent,
On 28 Mai, 18:12, Florent Hivert wrote:
> Just to let you know, I tried the following work around:
>
> ...
> but since A.toto.f.__name__ is still toto. It doesn't work. However the
> following works (on unpatched sage-4.6.2):
>
> def change_name(fun, name):
> fun = copy(fun)
>
Hi Florent,
On 27 Mai, 23:16, Florent Hivert wrote:
> Using the C class thing are even more weird:
>
> sage: c = C()
> sage: c.toto()
> [...]
> TypeError: toto() takes exactly 2 arguments (3 given)
I think I understand what happens in that case:
Inside c.toto(...), there is the line A.toto(self
Hi Simon,
> > But my patches do not solve the problem either -- only the error
> > message for b is different:
> > sage: b = B()
> > sage: b.toto()
> > 3
> > sage: b.toto()
> > Traceback (most recent call last):
> > ...
> > TypeError: toto() takes exactly 2 arguments (1 given)
> >
> > I can
Hi Simon,
> just for clarification: What you are reporting is the behaviour or
> unpatched Sage, i.e., it is not caused by my patches from #5,
> correct?
Sorry, for my unprecise bug report. I indeed had the problem with unpatched
sage 4.6.2.
> But my patches do not solve the problem ei
Hi Florent,
just for clarification: What you are reporting is the behaviour or
unpatched Sage, i.e., it is not caused by my patches from #5,
correct?
But my patches do not solve the problem either -- only the error
message for b is different:
sage: b = B()
sage: b.toto()
3
sage: b.toto()
Trac
Dear all,
First of all thanks to Simon for his optimization of the cached_method
decorator. Lots of code are now much faster. However it seems that there is a
problem using it with inheritance. I need to overload a cached method to
provide a default value for its argument. Here is a code rep
I don't think 4.6.2.alpha1 -> 4.7 or 4.6.2.alpha1 -> 4.7.alpha2 would work,
unless 4.6.2.alpha1 was released before Jeroen started his history-rewriting
prereleases. Essentially each new version (prerelease or otherwise) is
created by *backtracking to the latest stable release and readding all t
14 matches
Mail list logo
