Re: [Pythonmac-SIG] 2.4.3 Python Universal Binary Pystone Comparison

2006-04-07 Thread Ted Leung
Looks good here, too: [sprout:2012]> /Library/Frameworks/Python.framework/Versions/2.4/bin/ python -c "from test.pystone import pystones; print pystones()" (1.26, 39682.539682539682) === 2006-04-07 9:50 [sprout:2012]> /Library/Framewor

Re: [Pythonmac-SIG] 2.4.3 Python Universal Binary Pystone Comparison

2006-04-07 Thread Shane Holloway (IEEE)
Works great!! Thanks Ronald & crew! [EMAIL PROTECTED] ~% /Library/Frameworks/Python.framework/Versions/ 2.4/bin/python -c "from test.pystone import pystones; print pystones()" (1.6299, 30674.846625766873) Very exciting times in the Mac community all around. Looking forward to so

Re: [Pythonmac-SIG] 2.4.3 Python Universal Binary Pystone Comparison

2006-04-07 Thread Daniel Lord
;-( Thanks Ron--Not! Now my 1.8 Dual really looks long in the tooth at 3.0 pystones. Guess I need to buy a MacBook now that it runs rings around my clunky old desktop. It would be interesting to see how the dual core G5 and Quad core do as well as the 2+ Ghz newer duals. I know the origina

Re: [Pythonmac-SIG] 2.4.3 Python Universal Binary Pystone Comparison

2006-04-07 Thread Zachery Bir
On Apr 7, 2006, at 9:33 AM, Ronald Oussoren wrote: > I found some time to fire up the compiler. There's a new build of > the 2.4.3 installer on my iDisk. If that works correctly I'll ask > someone to replace the DMG on python.org. Please test if this > fixes the speed issues and works in ge

Re: [Pythonmac-SIG] 2.4.3 Python Universal Binary Pystone Comparison

2006-04-07 Thread Ronald Oussoren
On Friday, April 07, 2006, at 09:09AM, Ronald Oussoren <[EMAIL PROTECTED]> wrote: > >On Friday, April 07, 2006, at 08:10AM, Bob Ippolito <[EMAIL PROTECTED]> wrote: > >> It really has nothing to do with Xcode (or even GCC). This is all autoconf, >> but I'm pretty sure it was just that Ronald

Re: [Pythonmac-SIG] 2.4.3 Python Universal Binary Pystone Comparison

2006-04-07 Thread Ronald Oussoren
On Friday, April 07, 2006, at 08:10AM, Bob Ippolito <[EMAIL PROTECTED]> wrote: > It really has nothing to do with Xcode (or even GCC). This is all autoconf, > but I'm pretty sure it was just that Ronald had an OPT > environment variable set when he built it because I can't reproduce. See Mac

Re: [Pythonmac-SIG] 2.4.3 Python Universal Binary Pystone Comparison

2006-04-06 Thread Bob Ippolito
> Subject: Re: [Pythonmac-SIG] 2.4.3 Python Universal Binary Pystone Comparison Ok, I see what the problem is, because the Universal python is also half as fast on my PPC. It appears that the universal build is not using any compiler optimizations at all, where a normal build is -O3.  I'm

Re: [Pythonmac-SIG] 2.4.3 Python Universal Binary Pystone Comparison

2006-04-06 Thread Paul Berkowitz
Title: Re: [Pythonmac-SIG] 2.4.3 Python Universal Binary Pystone Comparison Maybe someone should ask on the Xcode mailing list. Almost every question is being answered there by the lead Xcode Tools Apple engineer, Chris Espinosa. -- Paul Berkowitz From: Bob Ippolito <[EMAIL PROTECTED]>

Re: [Pythonmac-SIG] 2.4.3 Python Universal Binary Pystone Comparison

2006-04-06 Thread Bob Ippolito
I can't reproduce this when I configure from the universal trunk, maybe Ronald had an OPT environment variable set when he built it?-bobOn Apr 6, 2006, at 10:34 PM, Bob Ippolito wrote:Ok, I see what the problem is, because the Universal python is also half as fast on my PPC.It appears that the univ

Re: [Pythonmac-SIG] 2.4.3 Python Universal Binary Pystone Comparison

2006-04-06 Thread Bob Ippolito
Ok, I see what the problem is, because the Universal python is also half as fast on my PPC.It appears that the universal build is not using any compiler optimizations at all, where a normal build is -O3.  I'm not quite sure where/why this is happening (autoconf is evil), but I'm sure someone will f

Re: [Pythonmac-SIG] 2.4.3 Python Universal Binary Pystone Comparison

2006-04-06 Thread Ted Leung
I just realized that I only sent this to Shane, so for the whole list (and Alex)Hmm.  Here's three of those...[sprout:2065]> ./python.exe -c "from test.pystone import pystones; print pystones()"(1.22, 40983.606557377047)=== 2006-04-06 18:0

Re: [Pythonmac-SIG] 2.4.3 Python Universal Binary Pystone Comparison

2006-04-06 Thread Daniel Lord
Just for fun I got the svn source and compiled it on my 1.8Ghz Dual G5 running 10.4.6 to add a data point:daniello ~/WIP/Python-Builds/py-24 ./python.exe -c "from test.pystone import pystones; print pystones()"(1.6199, 30864.1975308642)Better than the 1.86 GHZ MacBookPro but surprisingl

Re: [Pythonmac-SIG] 2.4.3 Python Universal Binary Pystone Comparison

2006-04-06 Thread Shane Holloway (IEEE)
Nice.  Very jealous about the Intel MacBook Pros.  :)  You both better put them to good use!  ;)Have either of you tried building the 2.4 release branch and running pystones from it?For those reading who may not know how from Terminal::svn co http://svn.python.org/projects/python/branches/release24

Re: [Pythonmac-SIG] 2.4.3 Python Universal Binary Pystone Comparison

2006-04-06 Thread Jordan Mantha
And here is mine on a 1.83GHz 17" Intel iMac:$ python -VPython 2.4.3$ python -c "from test.pystone import pystones; print pystones()"(1.99, 25125.628140703517)-Jordan ManthaOn Apr 6, 2006, at 2:36 PM, Ted Leung wrote:FWIW here are 3 runs from 1.83GHz MacBook Pro[sprout:2132]> /Library/Framework

Re: [Pythonmac-SIG] 2.4.3 Python Universal Binary Pystone Comparison

2006-04-06 Thread Ted Leung
FWIW here are 3 runs from 1.83GHz MacBook Pro[sprout:2132]> /Library/Frameworks/Python.framework/Versions/2.4/bin/python -c "from test.pystone import pystones; print pystones()"(2.0405, 24509.803921568622)=== 2006-04-06 14:

[Pythonmac-SIG] 2.4.3 Python Universal Binary Pystone Comparison

2006-04-06 Thread Shane Holloway (IEEE)
I was just wondering if anyone else had compared pystones on their box?  I downloaded the latest Universal Build from the python.org and found things to be a bit sluggish.  So I ran the pystones test to quickly gauge things, and noticed that things are indeed running about 1/3 of what they should b