Hi Daniel,
Thanks for putting this together. I am a huge supporter of benchmarking
efforts. My brief comment is below.
On Wed, Apr 6, 2011 at 11:52 AM, DasIch wrote:
>
> 1. Definition of the benchmark suite. This will entail contacting
> developers of Python implementations (CPython, PyPy, Ir
On Thu, Apr 7, 2011 at 6:11 PM, Michael Foord wrote:
> On 07/04/2011 22:41, Antoine Pitrou wrote:
>
>> On Thu, 07 Apr 2011 17:32:24 -0400
>> Tres Seaver wrote:
>>
>>> Right now, we are talking about building "speed.python.org" to test
the speed of python interpreters, over time, and alongsid
On Thu, Apr 7, 2011 at 6:52 PM, Michael Foord wrote:
>
>
*some* good benchmarks in place (and the pypy ones are good ones).
>
Agreed. The PyPy ones are good.
>
> So I'm still with Jesse on this one. If there is any "discussion phase" as
> part of the Gsoc project it should be very strictly boun
On Thu, Apr 7, 2011 at 8:29 PM, Jesse Noller wrote:
> On Thu, Apr 7, 2011 at 7:52 PM, Michael Foord
> wrote:
> > On 08/04/2011 00:36, Anthony Scopatz wrote:
> >
> > On Thu, Apr 7, 2011 at 6:11 PM, Michael Foord >
> > wrote:
> >>
> >> On 07/
>
>
> >
> >
> >> and will you complain if we don't provide a custom cython
> >> hacks? (like providing extra type information)
> >
> > I don't consider providing extra type information a hack. Remember that
> they
> > are only used for additional speed-ups in cases where the author is
> smarter
> >
