Here are my suggestions:
- While running bench marks don't listen to music, watch videos, use the
keyboard/mouse, or run anything other than the bench mark code. Seams like
common sense to me.
- I would average the timings of runs instead of taking the minimum value as
sometimes bench marks c
> Date: Tue, 11 Oct 2005 09:51:06 -0400 > From: Tim Peters <[EMAIL PROTECTED]>> Subject: Re: [Python-Dev] PythonCore\CurrentVersion > To: Martin v. L?wis <[EMAIL PROTECTED]>> Cc: python-dev@python.org > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1 > > [Tim Pet
ide it.
>
Bad idea unless it is tied to a namespace. So that users knows where this
auto-loaded functionality is coming from. Otherwise it's just as bad as 'from
xxx import *'.
John M. Camara
___
Python-Dev mailing list
Python-D
ll together?
If we go down this slippery slope we will see modules like array, struct, etc
getting referenced and getting auto loaded on behalf of the client. Where will
it end.
John M. Camara
> > Guido van Rossum writes:
> > Code that *doesn't* need Queue but does use th
as defined
in the standard library to have a different name if it wasn't just a queue.
Well I should have known better than to make assumption on this list. :)
I now see where Greg is coming from but I'm still not comfortable having
it in the threading module. To
be Queue belongs in a module called synchronize to avoid any confusions.
John M. Camara
___
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
