On Apr 7, 2005, at 07:49 PM, Frank Wierzbicki wrote:
> The developer guide suggests using Python 2.2 as the base, but since
> (I think) the ultimate goal over the next year is to try to reach
> parity with CPython, I'm wondering if, when we are looking at fixing
> up a failing test case, we should take a look at the CPython in CVS
> and see what can be done with the latest test case.
> To take a specific case, test_types.py is pretty close to functioning
> at against CVS CPython. There are a few problems with Longs and
> "buffer" appears to be completely unimplemented in Jython (I'm
> guessing this is deliberate since buffer has been in CPython for a
> long time but is doomed in Python 3000). If I could manage to get
> that test to pass, which would include conditionally ignoring the
> buffer tests, I could try to get the upstream CPython developers to
> accept the conditional ignore of buffer in their test_types.py, which
> would be nicer than maintaining our own.
I think as we work to target 2.3 this will be more realistic. I'm not
sure 2.2 is being maintained except for security fixes so it's unlikely
we'll be patching many test cases on that branch. It would be good to
begin submitting patches for 2.3 as we move Jython from 2.[1-2] to 2.3
but we need to continue finishing the new-style work. I think most
other implementors such as PyPy, IronPython and others are targeting
2.3 at least so our efforts right now are best spent finishing the
new-style work so we can begin moving to 2.3.
In general though I do think it would be much better for us to submit
patches to CPython's test suite to encourage re-use among the projects.
While at PyCon a number of us discussed identifying those tests which
targeted the core language and those which targeted additions or
enhancements or optional features.
It sounds like you're definitely thinking along the same lines.
Getting a common test suite is indeed something which all agree is a
> P.S. Is CPython still the accepted way to refer to the original
It's how I refer to it. I'm not sure what's the _correct_ way.