Is 4.0 a major breaking changes release?
I am still working on porting code from 2.x to 3.x. As of late on the lists I've seen comments about making somewhat major changes in 4.0 - now I'm concerned that I should pause my porting effort until that is released. Is python 4 going to be another python 3?
On Feb 3, 2018, at 17:40, Alex Walters <tritium-list@sdamon.com> wrote:
I am still working on porting code from 2.x to 3.x. As of late on the lists I've seen comments about making somewhat major changes in 4.0 - now I'm concerned that I should pause my porting effort until that is released. Is python 4 going to be another python 3?
At this point, Python 4 is just a convenient tag for really big changes. There are no concrete plans or schedule for such a major undertaking. Port away to Python 3.x! -- Ned Deily nad@python.org -- []
On 3 February 2018 at 22:40, Alex Walters <tritium-list@sdamon.com> wrote:
I am still working on porting code from 2.x to 3.x. As of late on the lists I've seen comments about making somewhat major changes in 4.0 - now I'm concerned that I should pause my porting effort until that is released. Is python 4 going to be another python 3?
No. Guido has gone on record as saying this won't happen. Paul
On Sat, Feb 3, 2018 at 4:40 PM, Alex Walters <tritium-list@sdamon.com> wrote:
I am still working on porting code from 2.x to 3.x. As of late on the lists I've seen comments about making somewhat major changes in 4.0 - now I'm concerned that I should pause my porting effort until that is released. Is python 4 going to be another python 3?
Emphatically no. Anyone suggesting big breaking changes in 4.0 is exercising wishful thinking :) There may be some cleanup in 4.0, but only removing things that have been deprecated for a long time in 3.x but hadn't been removed to maintain compatibility with 2.7. -- Zach
On Sat, Feb 3, 2018 at 2:40 PM, Alex Walters <tritium-list@sdamon.com> wrote:
I am still working on porting code from 2.x to 3.x. As of late on the lists I've seen comments about making somewhat major changes in 4.0 - now I'm concerned that I should pause my porting effort until that is released. Is python 4 going to be another python 3?
https://www.curiousefficiency.org/posts/2014/08/python-4000.html Python 0.x to 1.x was a small change. Python 1.x to 2.x was a small change. I doubt there'll be anything as important as str -> (bytes, unicode) to merit a breaking change.
On 2/3/2018 5:50 PM, Zachary Ware wrote:
On Sat, Feb 3, 2018 at 4:40 PM, Alex Walters <tritium-list@sdamon.com> wrote:
I am still working on porting code from 2.x to 3.x. As of late on the lists I've seen comments about making somewhat major changes in 4.0 - now I'm concerned that I should pause my porting effort until that is released. Is python 4 going to be another python 3?
Emphatically no. Anyone suggesting big breaking changes in 4.0 is exercising wishful thinking :)
There may be some cleanup in 4.0, but only removing things that have been deprecated for a long time in 3.x but hadn't been removed to maintain compatibility with 2.7.
So do your porting with deprecation warnings on. -- Terry Jan Reedy
On Sat, Feb 3, 2018 at 10:46 PM, Ned Deily <nad@python.org> wrote:
I am still working on porting code from 2.x to 3.x. As of late on the
On Feb 3, 2018, at 17:40, Alex Walters <tritium-list@sdamon.com> wrote: lists
I've seen comments about making somewhat major changes in 4.0 - now I'm concerned that I should pause my porting effort until that is released. Is python 4 going to be another python 3?
At this point, Python 4 is just a convenient tag for really big changes. There are no concrete plans or schedule for such a major undertaking. Port away to Python 3.x!
"Py3K?" they said, "oh, no, we're just noodling around with a few ideas ..." :-)
To be honest, and historically fair to Guido, he did warn for a long time that we should expect breaking changes in an eventual wart-removal release. It seemed to me the biggest disappointment was the team not having the resources to devote to a mooted but never really achieved reorganisation of the stdlib. Rectifying that omission would, I hope, be included as a priority in any Python 4 design. Since people rely on the stdlib hugely, automated translation of at least 98% of existing stdlib imports should be a goal. But that's just me.
On Sat, Feb 3, 2018 at 10:46 PM, Ned Deily <nad@python.org <mailto:nad@python.org>> wrote:
I've seen comments about making somewhat major changes in 4.0 - now I'm concerned that I should pause my porting effort until that is released. Is python 4 going to be another python 3?
Guido has repeatedly promised that there will never be another upheaval as big as the 2-to-3 one, and that the change from Python 3.9 to 4.0 won't be anything special. Hopefully we can trust him on that. -- Greg
participants (8)
-
Alex Walters -
Dan Stromberg -
Greg Ewing -
Ned Deily -
Paul Moore -
Steve Holden -
Terry Reedy -
Zachary Ware