On Fri, Oct 10, 2008 at 1:23 PM, Carl Friedrich Bolz wrote:

Ondrej Certik wrote:

...

On Mon, Sep 22, 2008 at 5:48 PM, Maciej Fijalkowski wrote:

...

I'm working on 2.5 compatibility branch right now. Due to incompatible changes, I suggest that we say we don't provide --pyversion option any more and simply compile 2.5 compatible interpreter. I don't really see benefits of providing 2.4 right now (after a brief discussion with Armin).

If anyone objects, please do that now.

Just a curious question --- what kind of features are python2.4 only that doesn't work in python2.5? I though that except hashing, python2.5 is backwards compatible.

I don't think there are any (big ones, at least). But that's just a further argument for removing the --pyversion option, isn't it?

Cheers,

Carl Friedrich

For example incompatible module APIs. They're kind of the same from user level, but the way they interact inside (for example sre and _sre) has changed. Cheers, fijal

2008/10/11 Ondrej Certik :

On Mon, Sep 22, 2008 at 5:48 PM, Maciej Fijalkowski wrote:

...

I'm working on 2.5 compatibility branch right now. Due to incompatible changes, I suggest that we say we don't provide --pyversion option any more and simply compile 2.5 compatible interpreter. I don't really see benefits of providing 2.4 right now (after a brief discussion with Armin).

If anyone objects, please do that now.

Just a curious question --- what kind of features are python2.4 only that doesn't work in python2.5? I though that except hashing, python2.5 is backwards compatible.

New style exceptions break a few things. A few deprecated things were removed -- OverflowWarning, for example. The idea that Python 3 was the first release of Python that isn't backwards compatible is slightly misleading :) Cheers, mwh