On 22 Jul, 2013, at 3:01, Larry Hastings la...@hastings.org 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.
On 22 Jul, 2013, at 1:36, Raymond Hettinger raymond.hettin...@gmail.com 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
On 22 Jul, 2013, at 1:46, Ben Hoyt benh...@gmail.com 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
On 22 Jul, 2013, at 7:35, Ned Deily n...@acm.org wrote:
In article 51ecae41.5060...@udel.edu, Terry Reedy tjre...@udel.edu
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
On Sun, 21 Jul 2013 16:36:35 -0700
Raymond Hettinger raymond.hettin...@gmail.com 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
On Mon, Jul 22, 2013 at 8:15 AM, Antoine Pitrou solip...@pitrou.net wrote:
On Sun, 21 Jul 2013 16:36:35 -0700
Raymond Hettinger raymond.hettin...@gmail.com 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
On Mon, Jul 22, 2013 at 9:32 AM, Maciej Fijalkowski fij...@gmail.com wrote:
On Mon, Jul 22, 2013 at 8:15 AM, Antoine Pitrou solip...@pitrou.net wrote:
On Sun, 21 Jul 2013 16:36:35 -0700
Raymond Hettinger raymond.hettin...@gmail.com wrote:
Our current Mac OS X builds use GCC-4.2.
On
Thanks for the insights, everyone.
--
~Ethan~
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
On 22 Jul, 2013, at 9:32, Maciej Fijalkowski fij...@gmail.com wrote:
On Mon, Jul 22, 2013 at 9:32 AM, Maciej Fijalkowski fij...@gmail.com wrote:
On Mon, Jul 22, 2013 at 8:15 AM, Antoine Pitrou solip...@pitrou.net wrote:
On Sun, 21 Jul 2013 16:36:35 -0700
Raymond Hettinger
Quoting Steve Dower steve.do...@microsoft.com:
As a Windows user, it makes me wonder if compiling with the latest
version of the Microsoft compiler
would improve things similarly?
I'd expect to see some improvement, based solely on the bugs fixed
recently by the optimizer team. No idea
I have opened an issue (http://bugs.python.org/issue18529) for patches.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
Yes, I meant to remove it. This function gnores errors in general.
2013/7/22 Eric V. Smith e...@trueblade.com:
[re-sending to python-dev]
On 7/21/2013 4:27 PM, benjamin.peterson wrote:
@@ -267,7 +267,7 @@
Py_DECREF(io);
Py_DECREF(binary);
On Mon, 2013-07-22 at 09:32 +0200, Maciej Fijalkowski wrote:
On Mon, Jul 22, 2013 at 9:32 AM, Maciej Fijalkowski fij...@gmail.com wrote:
On Mon, Jul 22, 2013 at 8:15 AM, Antoine Pitrou solip...@pitrou.net wrote:
On Sun, 21 Jul 2013 16:36:35 -0700
Raymond Hettinger
On Mon, 2013-07-22 at 17:15 +0200, Antoine Pitrou wrote:
Le Mon, 22 Jul 2013 11:08:32 -0400,
David Malcolm dmalc...@redhat.com a écrit :
How did this thread go from:
for OS X, GCC 4.8.1 gives you significantly faster machine code
than the system GCC 4.2.1
to
let's just use
On 22 Jul, 2013, at 17:08, David Malcolm dmalc...@redhat.com wrote:
On Mon, 2013-07-22 at 09:32 +0200, Maciej Fijalkowski wrote:
On Mon, Jul 22, 2013 at 9:32 AM, Maciej Fijalkowski fij...@gmail.com wrote:
On Mon, Jul 22, 2013 at 8:15 AM, Antoine Pitrou solip...@pitrou.net wrote:
On Sun, 21
Le Mon, 22 Jul 2013 11:08:32 -0400,
David Malcolm dmalc...@redhat.com a écrit :
How did this thread go from:
for OS X, GCC 4.8.1 gives you significantly faster machine code
than the system GCC 4.2.1
to
let's just use clang
?
Presumably if you want the faster possible machine code
[re-sending to python-dev]
On 7/21/2013 4:27 PM, benjamin.peterson wrote:
@@ -267,7 +267,7 @@
Py_DECREF(io);
Py_DECREF(binary);
PyMem_FREE(found_encoding);
-return PyErr_SetFromErrnoWithFilenameObject(PyExc_IOError, filename);
+return 0;
}
Hi,
A friend of mine, Ruadhan O'Flanagan, came across a bug which turned out
to be the one noted in [http://bugs.python.org/issue18019], i.e.:
d={}
d[42]=d.viewvalues()
d
segmentation fault
This issue has been fixed in hg; the behaviour now is that a
RuntimeError is produced for a recursive
On Mon, Jul 22, 2013 at 2:44 PM, Ben North b...@redfrontdoor.org wrote:
Hi,
A friend of mine, Ruadhan O'Flanagan, came across a bug which turned out
to be the one noted in [http://bugs.python.org/issue18019], i.e.:
d={}
d[42]=d.viewvalues()
d
segmentation fault
This issue has been
23.07.2013 00:01, Gregory P. Smith wrote:
On Mon, Jul 22, 2013 at 2:44 PM, Ben North b...@redfrontdoor.org
wrote:
A friend of mine, Ruadhan O'Flanagan, came across a bug which turned
out
to be the one noted in [http://bugs.python.org/issue18019 [1]],
i.e.:
d={}
d[42]=d.viewvalues()
d
Hi Greg,
Thanks for the feedback.
On 22 July 2013 23:01, Gregory P. Smith g...@krypto.org wrote:
On Mon, Jul 22, 2013 at 2:44 PM, Ben North b...@redfrontdoor.org wrote:
[... proposed change of behaviour such that a recursive
dictview gives a repr() with ... rather than a RuntimeError ...]
Could you please keep the comment # A symlink can never be a mount point
? It is useful. (I didn't know that, I'm not a windows developer.)
Victor
Le 22 juil. 2013 20:08, brian.curtin python-check...@python.org a
écrit :
http://hg.python.org/cpython/rev/240adc564539
changeset:
Add a new PyStructSequence_InitType2()
I added a new function because I guess that it would break the API (and
ABI) to change the return type of a function in a minor release.
Tell me if you have a better name than PyStructSequence_InitType2() ;-)
Ex suffix is usually used when parameters are
We've cheerfully broken the ABI before on minor releases, though if
it's part of the stable ABI, we can't be cavaliar about that anymore.
2013/7/22 Victor Stinner victor.stin...@gmail.com:
Add a new PyStructSequence_InitType2()
I added a new function because I guess that it would break the API
On Mon, Jul 22, 2013 at 6:36 PM, Victor Stinner
victor.stin...@gmail.com wrote:
Could you please keep the comment # A symlink can never be a mount point ?
It is useful. (I didn't know that, I'm not a windows developer.)
I don't think that's specific to Windows, but I added it back in
Just a suggestion from working with an assembly language stepper from a
while back with Intel x86...lost to an HD crash, but couldn't you
disassemble the binary, run through the assembly, and look for specific
instructions that you could refine into a simpler, smaller cycling time to
improve upon
26 matches
Mail list logo
