[issue4704] Update pybench for python 3.0

Antoine Pitrou added the comment: Committed in r69411, r69412. -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue4704] Update pybench for python 3.0

Antoine Pitrou 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.

[issue4704] Update pybench for python 3.0

Marc-Andre Lemburg added the comment: On 2009-02-06 23:25, Antoine Pitrou wrote: > Antoine Pitrou 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. > Shoul

[issue4704] Update pybench for python 3.0

Antoine Pitrou 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 tracker

[issue4704] Update pybench for python 3.0

Marc-Andre Lemburg added the comment: On 2009-02-06 18:35, Marc-Andre Lemburg wrote: > Marc-Andre Lemburg 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 this module compatible to

[issue4704] Update pybench for python 3.0

Marc-Andre Lemburg added the comment: Perfect ! Thanks, Antoine. Please check it in. On 2009-02-06 18:19, Antoine Pitrou wrote: > Antoine Pitrou added the comment: > > Updated patch. > > Added file: http://bugs.python.org/file12956/pybench3.0-3.patch > >

[issue4704] Update pybench for python 3.0

Antoine Pitrou added the comment: Updated patch. Added file: http://bugs.python.org/file12956/pybench3.0-3.patch ___ Python tracker ___ ___ Py

[issue4704] Update pybench for python 3.0

Marc-Andre Lemburg added the comment: On 2009-02-01 00:39, Antoine Pitrou wrote: > Antoine Pitrou 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 runtime

[issue4704] Update pybench for python 3.0

Antoine Pitrou 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 file: http://b

[issue4704] Update pybench for python 3.0

Antoine Pitrou 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 ___ _

[issue4704] Update pybench for python 3.0

Marc-Andre Lemburg added the comment: On 2008-12-22 15:07, Mark Dickinson wrote: > Mark Dickinson 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 remo

[issue4704] Update pybench for python 3.0

Mark Dickinson 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 that we could make

[issue4704] Update pybench for python 3.0

Marc-Andre Lemburg added the comment: On 2008-12-20 11:54, Mark Dickinson wrote: > New submission from Mark Dickinson : > > 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)

[issue4704] Update pybench for python 3.0

New submission from Mark Dickinson : 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 those that have chang