On Dec 29 2008, 8:36 am, prueba...@latinmail.com wrote:
> On Dec 23, 5:21 pm, Isaac Gouy wrote:
>
> > On Dec 23, 11:51 am, bearophileh...@lycos.com wrote:
>
> > > They have translated the Python benchmarks of theShootoutsite from
> > > Py2 to Py3 using 2to3:
>
> > >http://shootout.alioth.debian.or
On Dec 23, 5:21 pm, Isaac Gouy wrote:
> On Dec 23, 11:51 am, bearophileh...@lycos.com wrote:
>
> > They have translated the Python benchmarks of the Shootout site from
> > Py2 to Py3 using 2to3:
>
> >http://shootout.alioth.debian.org/u32/benchmark.php?test=all〈=pyt...
>
> So please re-write those
On Dec 23, 11:51 am, bearophileh...@lycos.com wrote:
> They have translated the Python benchmarks of the Shootout site from
> Py2 to Py3 using 2to3:
>
> http://shootout.alioth.debian.org/u32/benchmark.php?test=all〈=pyt...
So please re-write those programs to remove problems created by
automatic t
bearophileh...@lycos.com wrote:
They have translated the Python benchmarks of the Shootout site from
Py2 to Py3 using 2to3:
http://shootout.alioth.debian.org/u32/benchmark.php?test=all&lang=python3
It shows some "performance bugs" of Python3 itself (especially
regarding the binary-trees benchma
They have translated the Python benchmarks of the Shootout site from
Py2 to Py3 using 2to3:
http://shootout.alioth.debian.org/u32/benchmark.php?test=all&lang=python3
It shows some "performance bugs" of Python3 itself (especially
regarding the binary-trees benchmark, that was unexpected by me), an