Re: [Jython-dev] Should we go for 2.6 or 2.7 next?

[Stefan B. <ste...@be...>]

Colin Evans, 06.01.2010 20:55:
> Skipping python  
> versions that we have in production (ie going from 2.5 to 2.7) would  
> add to the (inaccurate) skepticism about whether jython is a 'real  
> python' that many of our python developers currently have.

Given that Python 2.x is officially a soon-to-be-dead platform, and given 
that 2.7 is basically supposed to add features that exist in Py3, but 
without breaking compatibility, I don't see the advantage of putting out a 
Py 2.6 and ignoring the new stuff that will make it into 2.7 anyway, i.e. 
into the officially last, compatible Py2 version ever.

Why not let Jython go for a 2.6+1/2 instead, i.e. a version compatible with 
the official CPython 2.6, but with additional features from the upcoming 
2.7. That way, code that targets 2.6 would run on Jython, but code that 
targets Jython specifically, or code written for the future CPython 2.7 
wouldn't be limited by artificial version borders. "We can't implement this 
feature because we are targeting 2.6" isn't a very convincing argument, 
IMHO, and "we can't accept your patch for that reason" doesn't sound very 
encouraging, either. Implementing 2.6 will take some time, so there may be 
quite some pending 2.7 patches by the time it's released.

Stefan