Alan Gauld wrote:
>> I can reproduce the problem on my Linux system, so it is not Mac
>> specific. Using xrange makes no difference.
>
> I believe that in recent Pythons (v2.3 onwards?) xrange is just
> an alias for range since range was reimplementted to use
> generators. So the old menory iss
> I can reproduce the problem on my Linux system, so it is not Mac
> specific. Using xrange makes no difference.
I believe that in recent Pythons (v2.3 onwards?) xrange is just
an alias for range since range was reimplementted to use
generators. So the old menory issues with range no longer
ap
On Sat, 2006-11-11 at 15:40 -0500, Joel Levine wrote:
> I'm using, perhaps misusing numpy which is eating up the memory and,
> eventually crashing my program.
I can reproduce the problem on my Linux system, so it is not Mac
specific. Using xrange makes no difference.
Oddly enough,
print
On Sat, 2006-11-11 at 15:40 -0500, Joel Levine wrote:
> I'm using, perhaps misusing numpy which is eating up the memory and,
> eventually crashing my program.
OK. that's a small enough piece of code to figure things out.
One quick suggestion, for looping variables xrange avoids creating a
real l
I'm using, perhaps misusing numpy which is eating up the memory and, eventually
crashing my program.
Isolating it, the following piece of code continually eats memory. Is it my
program or what ...?
Thanks
Joel Levine
Using Mac OSX 10.4.7
Not clear on versions: Appears to be 0.9.8 with py2.4
