On Wed, Dec 21, 2011 at 5:22 AM, Volker Braun wrote:
> How about the following implementation: If the return values is
> weakref-able, we store a weakref. Otherwise, we just store the object. Upon
> lookup, if the value is a weakref it is dereferenced.
>
> I now understand that @cached_method migh
On Wed, Dec 21, 2011 at 12:35 PM, Simon King wrote:
> Hi Volker,
>
> On 21 Dez., 21:05, Volker Braun wrote:
>> This is nowhttp://trac.sagemath.org/sage_trac/ticket/12215
>
> There are further tickets related with weak references
> * #11521 has already be mentioned
> * #715
> * #5970 (which is
On 12/21/11 12:48 PM, kcrisman wrote:
It turns out that askbot has two different possible settings for when
you click on "unanswered questions". It can mean "no accepted
answers" or "no answers". Currently, it's the former. I sort of feel
like that is confusing and it should be the other way,
Please check for the following issue:
1) Can you logout when using FF? I've seen problems with this on a Linux
box. Can anybody reproduce it? Otherwise, everything looks good to me.
Also, questions about handling the Jmol update as I will have some time
over the next week to work on that:
1)
Hi Volker,
On 21 Dez., 21:05, Volker Braun wrote:
> This is nowhttp://trac.sagemath.org/sage_trac/ticket/12215
There are further tickets related with weak references
* #11521 has already be mentioned
* #715
* #5970 (which is about the cache of polynomial rings).
I have patches for all three
On Wednesday, December 21, 2011 2:03:36 PM UTC, Simon King wrote:
>
> > Anyways, I haven't made a ticket yet.
> ... and then perhaps a weak cache for UniqueRepresentation could be
> discussed there.
>
This is now http://trac.sagemath.org/sage_trac/ticket/12215
--
To post to this group, send
It turns out that askbot has two different possible settings for when
you click on "unanswered questions". It can mean "no accepted
answers" or "no answers". Currently, it's the former. I sort of feel
like that is confusing and it should be the other way, but I'm not
strongly in favor of either
On Wed, Dec 21, 2011 at 8:07 AM, Jeroen Demeyer wrote:
> On Wed, Dec 21, 2011 at 07:46:27AM -0800, William Stein wrote:
>> I've been trying to use sage-4.8.alpha5 for daily work during the last
>> few days.
>
> Let me quote from
> http://boxen.math.washington.edu/home/release/sage-4.8.alpha5/READM
On Dec 21, 11:17 am, Volker Braun wrote:
> I'm pretty sure this ishttp://trac.sagemath.org/sage_trac/ticket/11963,
> which changed the aspect ratio handling. The default is now 1.0:
>
> sage: Graphics().aspect_ratio()
> 1.0
More precisely, when an empty graphics object is added to something
non
I'm pretty sure this is http://trac.sagemath.org/sage_trac/ticket/11963,
which changed the aspect ratio handling. The default is now 1.0:
sage: Graphics().aspect_ratio()
1.0
If you request 'automatic' then you get a plot of the specified
width/height:
sage: g.show(figsize=[8,4], aspect_ratio='
On Wed, Dec 21, 2011 at 07:46:27AM -0800, William Stein wrote:
> I've been trying to use sage-4.8.alpha5 for daily work during the last
> few days.
Let me quote from
http://boxen.math.washington.edu/home/release/sage-4.8.alpha5/README.FIRST:
This version of Sage is under construction, it has not
Hi,
I've been trying to use sage-4.8.alpha5 for daily work during the last
few days. I don't know what was done to plotting in sage-4.8.alpha5,
but it is seriously messed up.Basically, something is broken so
that figsize doesn't work at all. Often I have to set an aspect ratio
of 1000 just to
> I really wonder what those patches are about. AFAIK they are related to
> backporting changes to releases, but the need for this disappears
> completely if the upstream sources are all the time consistent with Sage.
Under the current development and testing model, that would be
extremely hard
Hi Volker,
On 21 Dez., 14:22, Volker Braun wrote:
> How about the following implementation: If the return values is
> weakref-able, we store a weakref. Otherwise, we just store the object. Upon
> lookup, if the value is a weakref it is dereferenced.
But that costs time, and I thus wouldn't like
On Tue, Dec 20, 2011 at 3:27 PM, kcrisman wrote:
> Because Sage may sometimes have custom patches to ECL that weren't in
> upstream at the time but are now, I don't know if it can be done 100%
> automatically.
I really wonder what those patches are about. AFAIK they are related to
backporting c
On Wed, Dec 21, 2011 at 4:23 AM, Dima Pasechnik wrote:
> do you like this to pull updates/patches from somewhere for testing, too?
> That's what the Sage's patchbot does, pulls patches from Sage's trac, and
> tests them.
> Or only "full releases"?
>
No, as I said in my original email, I would li
How about the following implementation: If the return values is
weakref-able, we store a weakref. Otherwise, we just store the object. Upon
lookup, if the value is a weakref it is dereferenced.
I now understand that @cached_method might be useful to cache the result of
a long computation even
Even with #11521, one gets
sage: import gc
sage: len(gc.get_objects())
164699
sage: for i in range(2,1000):
ring = ZZ.quotient(ZZ(i))
vectorspace = ring^2
:
sage: gc.collect()
63
sage: len(gc.get_objects())
375660
So, there is work to do.
However, I think using weak references in Uni
Hi Volker,
On 21 Dez., 13:08, Volker Braun wrote:
> You'll see that the size of __classcall__.cache increases dramatically.
> I've worked around this in my program by periodically purging stuff from
> the cache, but that shouldn't be the actual solution. I think
> * all "unique" objects should
I'm running a computation that uses lots of different vector spaces and
toric varieties, and it is eating ram like crazy. Although each parent is
only needed for a short time, it stays cached because they derive from
UniqueRepresentation. Now the documentation says that UniqueRepresentation
use
Back in 2008, I said I was interested in adding support for Clifford
algebras / Geometric Algebra to Sage. Since then I have found out that
there is some support available in Axiom. Now that there is renewed
interest in Exterior algebras, I would like to better understand how to
incorporate bot
On Wednesday, December 21, 2011 3:23:41 AM UTC, Dima Pasechnik wrote:
>
> That's what the Sage's patchbot does, pulls patches from Sage's trac, and
> tests them.
>
Just for the record, this is a completely separate automated testing
system: the build bot compiles potential releases on a variety
Thanks William and Rob for your feedback!
Cheers,
Nicolas
--
Nicolas M. Thiéry "Isil"
http://Nicolas.Thiery.name/
--
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...@goog
Hi Maarten,
I see this in Florian Hess's codes
###
# Genus
GffDifferentDeg := function(K)
local of, oi, df, di;
of := GffOrderMaxFinite(K);
oi := GffOrderMaxInfty(K);
df := GffOrderDisc(of);
di := GffOrderDisc(oi)
24 matches
Mail list logo
