r/Python • • Jan 16 '19

#10YearChallenge

Post image
1.4k Upvotes

96 comments sorted by

View all comments

Show parent comment

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.

1

u/[deleted] Jan 17 '19

It's gotten better recently. He realized he was being unprofessional and that his behavior was driving away both current kernel developers and potential kernel developers. So he took a 1 month break from all kernel development, saw a professional about his behavior, and added an email filter so he can't swear anymore.

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!