Re: [Python-Dev] Building a Faster Python

2013-07-21 Thread Antoine Pitrou
On Sun, 21 Jul 2013 16:36:35 -0700 Raymond Hettinger wrote: > Our current Mac OS X builds use GCC-4.2. > > On Python2.7, I ran a comparison of gcc-4.2.1 builds > versus gcc-4.8.1 and found that the latter makes a much > faster Python. PyBench2.0 shows the total running time > dropping from 5653m

Re: [Python-Dev] cpython (2.7): Issue #18441: Make test.support.requires('gui') skip when it should.

2013-07-21 Thread Ronald Oussoren
On 22 Jul, 2013, at 7:35, Ned Deily wrote: > In article <51ecae41.5060...@udel.edu>, Terry Reedy > wrote: >> > > This is exactly what Issue8716 was about. The buildbot has no way of > knowing ahead of time whether a test will cause a crash or not. Yes, Tk > should not crash but it does i

Re: [Python-Dev] Building a Faster Python

2013-07-21 Thread Ronald Oussoren
On 22 Jul, 2013, at 1:46, Ben Hoyt wrote: > > PyBench2.0 shows the total running time dropping from 5653ms to 4571ms. > > That's very cool -- a significant improvement. Is this the kind of change > that could go into 2.7.6 binaries? I'd prefer not to do that (but don't build the installers an

Re: [Python-Dev] Building a Faster Python

2013-07-21 Thread Ronald Oussoren
On 22 Jul, 2013, at 1:36, Raymond Hettinger wrote: > Our current Mac OS X builds use GCC-4.2. > > On Python2.7, I ran a comparison of gcc-4.2.1 builds > versus gcc-4.8.1 and found that the latter makes a much > faster Python. PyBench2.0 shows the total running time > dropping from 5653ms to 45

Re: [Python-Dev] Building a Faster Python

2013-07-21 Thread Ronald Oussoren
On 22 Jul, 2013, at 3:01, Larry Hastings wrote: > On 07/21/2013 04:36 PM, Raymond Hettinger wrote: >> Our current Mac OS X builds use GCC-4.2. >> >> On Python2.7, I ran a comparison of gcc-4.2.1 builds >> versus gcc-4.8.1 and found that the latter makes a much >> faster Python. PyBench2.0 show

Re: [Python-Dev] cpython (2.7): Issue #18441: Make test.support.requires('gui') skip when it should.

2013-07-21 Thread Ned Deily
In article <51ecae41.5060...@udel.edu>, Terry Reedy wrote: > On 7/21/2013 10:11 PM, R. David Murray wrote: > > On Mon, 22 Jul 2013 02:13:47 +0200, terry.reedy > > wrote: > >> +# If buildbot improperly sets gui resource (#18365, #18441), remove it > >> +# so requires('gui') tests are skipped whi

Re: [Python-Dev] [Python-checkins] cpython (2.7): Issue #18441: Make test.support.requires('gui') skip when it should.

2013-07-21 Thread R. David Murray
On Mon, 22 Jul 2013 02:13:47 +0200, terry.reedy wrote: > +# If buildbot improperly sets gui resource (#18365, #18441), remove it > +# so requires('gui') tests are skipped while non-gui tests still run. > +if use_resources and 'gui' in use_resources: Note that the buildbot cannot "improperly" set

Re: [Python-Dev] Building a Faster Python

2013-07-21 Thread Larry Hastings
On 07/21/2013 04:36 PM, Raymond Hettinger wrote: Our current Mac OS X builds use GCC-4.2. On Python2.7, I ran a comparison of gcc-4.2.1 builds versus gcc-4.8.1 and found that the latter makes a much faster Python. PyBench2.0 shows the total running time dropping from 5653ms to 4571ms. The code

Re: [Python-Dev] Building a Faster Python

2013-07-21 Thread Raymond Hettinger
On Jul 21, 2013, at 5:32 PM, Ned Deily wrote: > In article <252c50d8-c23d-438d-bae1-b22e0d65a...@gmail.com>, > Raymond Hettinger wrote: >> Our current Mac OS X builds use GCC-4.2. >> >> On Python2.7, I ran a comparison of gcc-4.2.1 builds >> versus gcc-4.8.1 and found that the latter makes a m

Re: [Python-Dev] Building a Faster Python

2013-07-21 Thread Ned Deily
In article <252c50d8-c23d-438d-bae1-b22e0d65a...@gmail.com>, Raymond Hettinger wrote: > Our current Mac OS X builds use GCC-4.2. > > On Python2.7, I ran a comparison of gcc-4.2.1 builds > versus gcc-4.8.1 and found that the latter makes a much > faster Python. PyBench2.0 shows the total running

Re: [Python-Dev] Building a Faster Python

2013-07-21 Thread Steve Dower
>From: Ben Hoyt >> PyBench2.0 shows the total running time dropping from 5653ms to 4571ms. > > That's very cool -- a significant improvement. Is this the kind of change > that could go into 2.7.6 binaries? > > As a Windows user, it makes me wonder if compiling with the latest version of > the M

Re: [Python-Dev] Building a Faster Python

2013-07-21 Thread Brian Curtin
On Sun, Jul 21, 2013 at 6:46 PM, Ben Hoyt wrote: >> PyBench2.0 shows the total running time dropping from 5653ms to 4571ms. > > That's very cool -- a significant improvement. Is this the kind of change > that could go into 2.7.6 binaries? > > As a Windows user, it makes me wonder if compiling with

Re: [Python-Dev] Building a Faster Python

2013-07-21 Thread Ben Hoyt
> PyBench2.0 shows the total running time dropping from 5653ms to 4571ms. That's very cool -- a significant improvement. Is this the kind of change that could go into 2.7.6 binaries? As a Windows user, it makes me wonder if compiling with the latest version of the Microsoft compiler would improve

[Python-Dev] Building a Faster Python

2013-07-21 Thread Raymond Hettinger
Our current Mac OS X builds use GCC-4.2. On Python2.7, I ran a comparison of gcc-4.2.1 builds versus gcc-4.8.1 and found that the latter makes a much faster Python. PyBench2.0 shows the total running time dropping from 5653ms to 4571ms. The code is uniformly better in just about every category.