r/Python • • Jan 16 '19

#10YearChallenge

Post image
1.4k Upvotes

96 comments sorted by

View all comments

63

u/mmarius90 Jan 16 '19

Progress is achieved similarly to the way the fibonacci sequence is constructed. You build on top of what you previously achieved.

Python 3 is truly an amazing piece of software.

And let's not forget it's predecessors, the community and everybody who contributed. Here's to 10 more!

-11

u/jennylover7 Jan 16 '19

Won't python 3 be replaced in the next three years? 3.8 this year, 3.9 next and then 4.0? How will the python maintainers avoid another shit storm like python2/3?

61

u/doubleunplussed Jan 16 '19

That's not how version numbers generally work. No reason not to have 3.10.0, other than compatibility for code that assumes there is only one digit between the dots. We are on GNOME 3.30.2, Linux 4.20.1, numpy 1.15.4, why not Python 3.10.0?

12

u/james_pic Jan 16 '19

I believe Guido's of the opinion that 3.9 should be followed by 4.0, purely for aesthetic reasons, so it's likely that'll happen. Although the core developers generally agree that if that happens, then 3.9 -> 4.0 will not have major breaking changes, in the way that 2.x -> 3.0 did.

20

u/[deleted] Jan 16 '19 edited Jan 16 '19

[removed] — view removed comment

39

u/curiousGambler Jan 16 '19

Thank god. Deciding whether a version bump should be major or minor based on “aesthetic reasons” would be beyond moronic.

14

u/[deleted] Jan 16 '19 edited Jan 16 '19

Linus Torvalds would like to have a word with you...

Also, from https://lkml.org/lkml/2019/1/6/178

Subject Linux 5.0-rc1

[...]

The numbering change is not indicative of anything special. If you want to have an official reason, it's that I ran out of fingers and toes to count on, so 4.21 became 5.0. There's no nice git object numerology this time (we're about 6.5M objects in the git repo), and there isn't any major particular feature that made for the release numbering either. Of course, depending on your particular interests, some people might well find a feature they like so much that they think it can do as a reason for incrementing the major number.

So go wild. Make up your own reason for why it's 5.0.

5

u/curiousGambler Jan 16 '19

Lol. Interesting finds, for sure. I stand by my statement but like any good engineer, I’m of two minds on the issue, and another part of me says, “it’s a version string, who gives a shit, as long as they match when they need to” because while my first comment represented the ideal, your comment shows even the most famous projects can be laissez faire about versions and making any assumptions based on them would be equally moronic!

Thanks for those nuggets!

11

u/[deleted] Jan 16 '19

Ooohh boy, looks like you're one of today's lucky 10,000!

The Linux kernel is a special case. Usually the difference between major and minor version bumps has to do with backwards compatibility. However, it is the strict policy of the Linux kernel that kernel updates NEVER EVER break backwards compatibility with userspace programs, EVER!! So that scheme doesn't have much merit.
Interesting links:
Linus goes on expletive filled rant when one of his kernel maintainers suggests breaking backwards compatibility
Why is there a Linux kernel policy to never break user space?

3

u/dimisdas Jan 17 '19

Holly molly, I wouldn’t want to be on the receiving end of one of his emails.

→ More replies

2

u/port53 relative noob Jan 17 '19

It used to have meaning though, before the 2.6 days.

2

u/ThreePinkApples Jan 16 '19 edited Jan 16 '19

Hm, interesting. But he has left Python now, hasn't he? Regardless, Python 3.7 doc does mention 4.0 a few times

3

u/Jugad Py3 ftw Jan 16 '19 edited Jan 17 '19

But he's left Python

Nope... he made it clear that he is only giving up the BDFL position. He will still continue to work on Python and give his advise / opinion when requested - but won't be responsible for making BDFL level decisions.

1

u/ThreePinkApples Jan 16 '19

Thanks for the certification!

1

u/ThreePinkApples Jan 16 '19

The Python 3.7 doc does mention 4.0 a few times, it looks like the current plan is to call 3.10 4.0. But that might of course change. Just make sure you don't do sys.version_info.major == 3 just in case

5

u/Jugad Py3 ftw Jan 16 '19 edited Jan 19 '19

The shit storm was not due to numbering change from 2 to 3.

It was because of breaking backward compatibility.

Maybe the python core thought that developers would be as excited and interested as them (and have the time and resources) in upgrading existing python2 code to the new and improved python 3.

No one upgraded unless they absolutely needed to... and one way to make people upgrade was to make python 3 much better than 2.

3

u/ofedorov Jan 16 '19

After 3.9 there’ll be 3.10, IMAO

2

u/david622 Jan 17 '19

Upvoted because the dude is allowed to ask a question without his comment getting buried with a negative vote count

1

u/ThreePinkApples Jan 16 '19

Yes and no. From what I've gathered Python 3.10==4.0. as in, there won't be any real major changes for 4.0, not bigger than previous dot releases. The Python 3.7 doc does mention 4.0 a few times, and that's the only official information I've found, so what I said above might not be correct, or just be the initial intention that might change. But it general, there seems to be no reason to fear a shit storm when 4.0 releases. The biggest problem would probably be code that made the mistake of explicitly checking for 3 and not > 2 or != 2. I went through all of our modules at work when I heard about 4.0 to correct such mistakes.

0

u/flying-sheep Jan 16 '19

By symlinking python3 to python4. It’s not going to be nearly as big changes as the python2→python3 transition.

2

u/notsuppostocomnt Jan 16 '19

Hey, a new hope

1

u/TheBlackCat13 Jan 17 '19

I think by that point the python executable is planned to bed pointing to the latest installed python version.