[sage-devel] Re: Can we afford a new attribute of sage.structure.element.Element?

Hi Nils, On 30 Apr., 19:12, Nils Bruin wrote: > I looked over the comments in trac #5 . Thank you for a very > thorough analysis and presentation. One thing I didn't immediately > find in the discussion there is that an increased memory footprint for > elements can also cause cache-misses soo

[sage-devel] Re: [sage-notebook] The crazy NB bug

On 4/30/11 3:22 PM, kcrisman wrote: For the record I have been using flask.sagenb.org daily to prepare all my lectures and have not once seen this problem. My hope is that we fixed it in the flask notebook by keeping better track of when a text cell was added. This has been my experience.

[sage-devel] Re: [sage-notebook] The crazy NB bug

> >> For the record I have been using flask.sagenb.org daily to prepare all > >> my lectures and have not once seen this problem. > > > My hope is that we fixed it in the flask notebook by keeping better track of > > when a text cell was added. > > This has been my experience.  It is unclear if it

[sage-devel] Puiseux Series Implementation Location

Hello, I recently implemented Puiseux series expansions in Sage and I would like to make this available in Sage to everyone. However, I was hoping for some suggestions as to where to place this code before I go any further. First of all, Puiseux series (wiki

[sage-devel] Suggestions for Puiseux Expansion Implementation Location

Hello, I recently implemented Puiseux series expansions in Sage and I would like to make this available in Sage to everyone. However, I was hoping for some suggestions as to where to place this code before I go any further. First of all, Puiseux series (wiki

[sage-devel] Re: Can we afford a new attribute of sage.structure.element.Element?

Hi Simon, I looked over the comments in trac #5 . Thank you for a very thorough analysis and presentation. One thing I didn't immediately find in the discussion there is that an increased memory footprint for elements can also cause cache-misses sooner, so lead to a slowdown (so memory usage c

[sage-devel] Someone is spoofing my email address.

If you get an email that appears to come from me, that looks silly, then please send me a private email. I'm not exactly sure what has happened. Whether someone has hacked my account and so sending mail form there, or if they are just spoofing the "From" field. But at least a couple of people ha

Re: [sage-devel] Re: XCode 4

On 04/30/11 04:27 PM, Dima Pasechnik wrote: On Apr 30, 12:54 pm, William Stein wrote: Even worse is behaviour with its clang compilers (they can't even compile several parts of Sage) Wow, that's incredible! We should: (1) add a remark right in the prereq spkg that checks that xcode 4

[sage-devel] Re: XCode 4

I edited http://wiki.sagemath.org/SupportedPlatforms to reflect the status of XCode 4. On Apr 30, 11:27 pm, Dima Pasechnik wrote: > On Apr 30, 12:54 pm, William Stein wrote: > > > > > > > On Wed, Apr 27, 2011 at 8:28 PM, Dima Pasechnik wrote: > > > Hi, > > > > I tried XCode 4 and came to conclu

[sage-devel] Re: XCode 4

On Apr 30, 12:54 pm, William Stein wrote: > On Wed, Apr 27, 2011 at 8:28 PM, Dima Pasechnik wrote: > > Hi, > > > I tried XCode 4 and came to conclusion that it is buggy as hell > > - I can't build working Sage (due to startup-time segfaults, as > > described here), > > I can't even build a workin

[sage-devel] Re: Can we afford a new attribute of sage.structure.element.Element?

Hi Nicolas, On 29 Apr., 23:06, "Nicolas M. Thiery" wrote: > Can you give it a shot with GF(2), so as to hit one of the smallest > possible sage Element? Sage-4.7.alpha5 with patches: sage: K = GF(2) sage: get_memory_usage() 842.01171875 sage: %time L = [K(i) for i in xrange(10^7)] CPU times: us