[Python-Dev] [GSoC] Developing a benchmark suite (for Python 3.x)

[Maciej Fijalkowski]

On Fri, Apr 8, 2011 at 11:22 AM, Stefan Behnel <stefan_ml at behnel.de> wrote:
> Jesse Noller, 07.04.2011 22:28:
>>
>> On Thu, Apr 7, 2011 at 3:54 PM, Anthony Scopatz wrote:
>>>
>>> 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, IronPython and
>>>> Jython), via discussion on the appropriate mailing lists. This might
>>>> be achievable as part of this proposal.
>>>>
>>>
>>> If you are reaching out to other projects at this stage, I think you
>>> should
>>> also be in touch with the Cython people  (even if its 'implementation'
>>> sits on top of CPython).
>>> As a scientist/engineer what I care about is how Cython benchmarks to
>>> CPython.  I believe that they have some ideas on benchmarking and have
>>> also explored this space.  Their inclusion would be helpful to me
>>> thinking
>>> this GSoC successful at the end of the day (summer).
>>> Thanks for your consideration.
>>> Be Well
>>> Anthony
>>
>> Right now, we are talking about building "speed.python.org" to test
>> the speed of python interpreters, over time, and alongside one another
>> - cython *is not* an interpreter.
>
> Would you also want to exclude Psyco then? It clearly does not qualify as a
> Python interpreter.
>

Just to clarify - the crucial word here is Python and not the
interpreter. I don't care myself if it's an interpreter or a compiler,
I do care if it can pass the python test suite (modulo things that are
known to be implementation details and agreed upon).

How far is Cython from passing the full test suite? Are there known
incompatibilities that would be considered wontfix?

Cheers,
fijal