RetroSearch Browse

Fri Nov 30 13:10:21 EST 2018 · https://mail.python.org/pipermail/python-dev/2018-November/155903.html

Steve Dower wrote:
> My proposed marketing pitch is: "rewrite your existing code to be 
> forward-compatible today and faster in the future without more work, or 
> be prepared to rewrite/update your source code for each CPython release 
> to remain compatible with the low level API". The promise of "faster in 
> the future" needs to be justified (and I think there's plenty of 
> precedent in PyPy, Larry's Gilectomy and the various JavaScript VMs to 
> assume that we can do it).

It's hard to discuss this in the abstract without knowing how big the
breakage between each version is going to be.

But for the scientific ecosystem this sounds a bit like a potential
Python-4.0 breakage, which was universally rejected (so far).

In the extreme case I can imagine people staying on 3.7.

But it really depends on the nature of the changes.

Stefan Krah

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2018-November/155903.html below:

[Python-Dev] C API changes