On Aug 11, 2:09 pm, [EMAIL PROTECTED] wrote:
> On Aug 11, 10:55 am, [EMAIL PROTECTED] wrote:
>
>
>
> > On Aug 10, 10:10 pm, Kris Kennaway <[EMAIL PROTECTED]> wrote:
>
> > > jlist wrote:
> > > > I think what makes more sense is to compare the code one most
> > > > typically writes. In my case, I alw
On Aug 10, 10:10 pm, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> jlist wrote:
> > I think what makes more sense is to compare the code one most
> > typically writes. In my case, I always use range() and never use psyco.
> > But I guess for most of my work with Python performance hasn't been
> > a is
On Aug 7, 2:52 pm, [EMAIL PROTECTED] wrote:
> On Aug 7, 6:38 am, [EMAIL PROTECTED] wrote:
>
> > On Aug 7, 2:05 am, "Jack" <[EMAIL PROTECTED]> wrote:
>
> > > I know one benchmark doesn't mean much but it's still disappointing to see
> > > Python as one of the slowest languages in the test:
>
> > >ht
On Aug 7, 5:05 am, "Jack" <[EMAIL PROTECTED]> wrote:
> I know one benchmark doesn't mean much but it's still disappointing to see
> Python as one of the slowest languages in the test:
>
> http://blog.dhananjaynene.com/2008/07/performance-comparison-c-java-p...
I was actually disappointed myself wi
On Aug 7, 12:44 pm, alex23 <[EMAIL PROTECTED]> wrote:
> Steven D'Aprano wrote:
> > In other words, about 20% of the time he measures is the time taken to
> > print junk to the screen.
>
> Which makes his claim that "all the console outputs have been removed
> so that the benchmarking activity is no
On Aug 7, 6:38 am, [EMAIL PROTECTED] wrote:
> On Aug 7, 2:05 am, "Jack" <[EMAIL PROTECTED]> wrote:
>
> > I know one benchmark doesn't mean much but it's still disappointing to see
> > Python as one of the slowest languages in the test:
>
> >http://blog.dhananjaynene.com/2008/07/performance-comparis
