Michele Petrazzo wrote:
> [EMAIL PROTECTED] wrote:
> > Michele Petrazzo wrote:
> >> I haven't tried to recompile py 2.4 myself with gcc 4.1 because it
> >> is already compiled with it (4.0.3), so I think (only think) that
> >> is a py 2.5 problem. I'm right? or I have to compile it with
> >> someth
[EMAIL PROTECTED] wrote:
> Michele Petrazzo wrote:
>> I haven't tried to recompile py 2.4 myself with gcc 4.1 because it
>> is already compiled with it (4.0.3), so I think (only think) that
>> is a py 2.5 problem. I'm right? or I have to compile it with
>> something other switches?
>
> Sounds l
Michele Petrazzo wrote:
> Then I execute my test. The memory usage of 2.5a2 and gcc 3.3 that I
> see with "top", is the same (about VIRT: 260 MB and RES: 250MB ) that
> with the py 2.3 and 2.4, but then I recompile with 4.1 and execute
> the same test, my system "stop to work"... with "top" I can
[Michele Petrazzo]
> I'm doing some tests on my debian testing and I see a very strange
> memory problem with py 2.5a2 (just downloaded) and compiled with gcc
> 4.1.0, but not with the gcc 3.3.5:
>
> My test are:
>
> #--test.py
> import sys
> if sys.version.startswith("2.3"):
> from sets import S
Michele Petrazzo wrote:
>
> I haven't tried to recompile py 2.4 myself with gcc 4.1 because it is
> already compiled with it (4.0.3), so I think (only think) that is a py
> 2.5 problem.
> I'm right? or I have to compile it with something other switches?
Sounds like a gcc problem to me. Try adding
Hi list,
I'm doing some tests on my debian testing and I see a very strange
memory problem with py 2.5a2 (just downloaded) and compiled with gcc
4.1.0, but not with the gcc 3.3.5:
My test are:
#--test.py
import sys
if sys.version.startswith("2.3"):
from sets import Set as set
b=set(range(50
