Code that will break in Python 4

#1

Post by astrofrog » Tue, Jan 12, 2016, 3:48 PM UTC

Code that will break in Python 4
astrofrog.github.io

Re: Code that will break in Python 4

#2

Post by stefs » Tue, Jan 12, 2016, 4:17 PM UTC

don't be silly - my code will long be replaced when python 4 comes out! it's just a temporary hack/short term solution anyway.

Re: Code that will break in Python 4

#3

Post by [deleted] » Tue, Jan 12, 2016, 4:20 PM UTC

[deleted]

Re: Code that will break in Python 4

#4

Post by ctz » Tue, Jan 12, 2016, 4:20 PM UTC

Has there actually been a statement that python 4 will be backwards compatible to python 3?

Re: Code that will break in Python 4

#5

Post by to3m » Tue, Jan 12, 2016, 4:21 PM UTC

2020! I wonder if I'll have more luck finding the time to upgrade my python 2 scripts in the next four years than I've had in the last four?

Re: Code that will break in Python 4

#6

Post by rudolf0 » Tue, Jan 12, 2016, 4:22 PM UTC

ctz wrote: post #4

Has there actually been a statement that python 4 will be backwards compatible to python 3?

Formally, no, but Guido expressed regret that Python 3 broke backwards compatibility, and made intentions of trying to minimize backwards incompatibility for Python 4.

Re: Code that will break in Python 4

#7

Post by mpdehaan2 » Tue, Jan 12, 2016, 4:24 PM UTC

No problem! I've already fixed it so that all my code is forward compatible with Python 7000, despite not knowing what any of the syntax or library changes are going to look like.

Re: Code that will break in Python 4

#8

Post by untothebreach » Tue, Jan 12, 2016, 4:24 PM UTC

ctz wrote: post #4

Has there actually been a statement that python 4 will be backwards compatible to python 3?

I don't have any links but I know there have been statements by core devs that, when/if there is another major version of python being developed, there will be an upgrade path to make the 3->4 transition much better than the 2->3 transition.

Re: Code that will break in Python 4

#9

Post by gh02t » Tue, Jan 12, 2016, 4:24 PM UTC

ctz wrote: post #4

Has there actually been a statement that python 4 will be backwards compatible to python 3?

I believe they said they were going to try very hard to not do major backwards compatible breaking changes again.

> My current expectation is that Python 4.0 will merely be "the release that comes after Python 3.9". That's it. No profound changes to the language, no major backwards compatibility breaks - going from Python 3.9 to 4.0 should be as uneventful as going from Python 3.3 to 3.4 (or from 2.6 to 2.7). I even expect the stable Application Binary Interface (as first defined in PEP 384) to be preserved across the boundary.

http://www.curiousefficiency.org/posts/2014/08/python-4000.h... (which was linked by Guido from his Twitter).

Re: Code that will break in Python 4

#10

Post by mrmb » Tue, Jan 12, 2016, 4:25 PM UTC

ctz wrote: post #4

Has there actually been a statement that python 4 will be backwards compatible to python 3?

From Guido: he expects "Python 4.0 will merely be "the release that comes after Python 3.9". That's it. No profound changes to the language, no major backwards compatibility breaks"

http://www.curiousefficiency.org/posts/2014/08/python-4000.h...

Would be nice if it was simply 3.10 not 4.0, as there's much discussion on that too.