Sebastien Maret wrote:
> Kurt Schwehr <[EMAIL PROTECTED]> writes:
>
>
>> I have two mac boxes... on my G5 machine, all pythons
>> are slow to start:
>>
>> time python2.4 -c "pass"
>>
>> real0m2.726s
>>
>> time /usr/bin/python -c "pass"
>>
>> real0m2.909s
>> user0m0.023s
>> sys 0
Kurt Schwehr <[EMAIL PROTECTED]> writes:
> I have two mac boxes... on my G5 machine, all pythons
> are slow to start:
>
> time python2.4 -c "pass"
>
> real0m2.726s
>
> time /usr/bin/python -c "pass"
>
> real0m2.909s
> user0m0.023s
> sys 0m2.719s
>
> But on my G4 laptop I get a rea
This is just a stab in the dark (no, I don't know how to get more
detail from ktrace/kdump), but could some of the system .pyc files be
out of date wrt the .py files?
Also, what if you try it with a minimal $PATH?
Any DYLD_* environment variables set?
You can also try fs_usage to compare filesys
On Dec 19, 2006, at 8:06 AM, Kurt Schwehr wrote:
> Hi All,
>
> I have two mac boxes... on my G5 machine, all pythons
> are slow to start:
>
> time python2.4 -c "pass"
>
> real0m2.726s
>
> time /usr/bin/python -c "pass"
>
> real0m2.909s
> user0m0.023s
> sys 0m2.719s
>
> But on my
Hi All,
I have two mac boxes... on my G5 machine, all pythons
are slow to start:
time python2.4 -c "pass"
real0m2.726s
time /usr/bin/python -c "pass"
real0m2.909s
user0m0.023s
sys 0m2.719s
But on my G4 laptop I get a real time of 0.09-0.15s
which is much more acceptable, but
