Antoine Pitrou pit...@free.fr added the comment:
If possible, pybench should work unchanged in both Python 2.x and 3.x.
Ok, the best I can do is to make it 2.6-compatible. For versions before
2.6, stuff like except Exception as e does not make compatibility
reasonably achievable.
Antoine Pitrou pit...@free.fr added the comment:
Committed in r69411, r69412.
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4704
___
Antoine Pitrou pit...@free.fr added the comment:
Updated patch.
Added file: http://bugs.python.org/file12956/pybench3.0-3.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4704
___
Marc-Andre Lemburg m...@egenix.com added the comment:
On 2009-02-06 18:35, Marc-Andre Lemburg wrote:
Marc-Andre Lemburg m...@egenix.com added the comment:
Perfect ! Thanks, Antoine. Please check it in.
Well, except for this part that sneaked in:
@@ -4,8 +4,6 @@
#
-# Note: Please keep
Antoine Pitrou pit...@free.fr added the comment:
It's ok to bump this to Python 2.3, though :-)
The current version only works with 3.x, due to the use of the print
function with the end keyword argument.
Should it be fixed?
Regards
Antoine.
___
Python
Marc-Andre Lemburg m...@egenix.com added the comment:
On 2009-02-01 00:39, Antoine Pitrou wrote:
Antoine Pitrou pit...@free.fr added the comment:
The patch changes results a lot compared to the previous version
(BuiltinFunctionCalls is 3x slower). I propose the following patch,
which gives
Antoine Pitrou pit...@free.fr added the comment:
The patch changes results a lot compared to the previous version
(BuiltinFunctionCalls is 3x slower). I propose the following patch,
which gives roughly the same runtimes as before (I use divmod() and
max() rather than complex() and pow()).
Added
Antoine Pitrou pit...@free.fr added the comment:
Since cmp is slated for removal, this should also be done for 3.0.1.
--
nosy: +pitrou
priority: - release blocker
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4704
Mark Dickinson dicki...@gmail.com added the comment:
Thanks for the responses!
I don't think should go into 3.0.1 - they are a new feature
and not a bug fix.
But if these changes don't go into 3.0.1, and the removal of cmp does,
that means that pybench won't run on 3.0.1. It seems to me
Marc-Andre Lemburg m...@egenix.com added the comment:
On 2008-12-22 15:07, Mark Dickinson wrote:
Mark Dickinson dicki...@gmail.com added the comment:
Thanks for the responses!
I don't think should go into 3.0.1 - they are a new feature
and not a bug fix.
But if these changes don't go
New submission from Mark Dickinson dicki...@gmail.com:
pybench needs to be updated for Python 3.0, in particular to remove use of
cmp. Here's a patch, against the py3k branch.
Questions (mainly for Marc-André Lemburg):
1. Should the version number be bumped for *all* tests, or just for
Marc-Andre Lemburg m...@egenix.com added the comment:
On 2008-12-20 11:54, Mark Dickinson wrote:
New submission from Mark Dickinson dicki...@gmail.com:
pybench needs to be updated for Python 3.0, in particular to remove use of
cmp. Here's a patch, against the py3k branch.
Questions
12 matches
Mail list logo
