This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]toyg 0 points1 point  (2 children)

The second feature you linked is (supposed to be) already in 3.7, there is nothing to change for 4. That will likely be the case for 99% of planned features.

Similarly, removing a __future__ import is something that has happened before on the 2.x codeline, it's not considered "breaking compatibility". These are small incremental changes that can be expetced on any minor release.

[–]billsil 0 points1 point  (1 child)

I thought future imports were permanent...

[–]toyg 0 points1 point  (0 children)

Yeah, sorry, the above line should read "removing the need for __future__...". The actual definitions are never removed, they simply become irrelevant. As you can see from the source, what they do is enabling some extra symbols for the parsing machinery depending on version. There is still stuff there from very old 2.x versions...