r/Python • Freelancer. AnyFactor.xyz • Sep 16 '20

News An update on Python 4

Post image
3.3k Upvotes

389 comments sorted by

View all comments

-7

u/productive_guy123 Sep 16 '20

Why didn’t they refer to the version as 3.09 rather than 3.9

30

u/[deleted] Sep 16 '20 edited Sep 16 '20

Because version numbers aren't decimals. The points just separate major and minor versions, and often things like patch versions. There's plenty of software with more than two sections of the version, like 2.15.7. As it happens the app I work on just bumped from a x.x.9 to x.x.10 this week.

Edit: not sure why you're getting downvoted for asking this. It's a totally fair question if you don't have a lot of experience with development.

9

u/duncan-udaho Sep 16 '20

This is correct. It's not a decimal number. It's a version number, probably a semantic version number, which prohibits leading zeros and in fact specifically calls out this case. 1.9.0 -> 1.10.0

2

u/productive_guy123 Sep 17 '20

Thanks for the explanation, I honestly don’t know why though

2

u/[deleted] Sep 17 '20

People just like to feel superior I guess. To make the case even better how reasonable the question is: I'm the person who decided our version convention and even decide in most cases how we break up releases into patches and minor versions, so you would think I would be pretty intimately aware of how it all works. I happened to need to write a simple function recently that compared version numbers and my immediate impulse was just to convert it to decimals (with major version being hundreds). I realized right after writing it out that I couldn't count on there being less than 100 patches or minor versions, but it goes to show that even if you are very familiar with it, thinking about it the way you did is totally natural.

33

u/Sw429 Sep 16 '20

Why not refer to it as 3.009 just in case Python 3 has 100 versions? But then what if it has 1000 versions?

It's just too hard to predict. Most version numbering handles this the way python is.

9

u/Erelde Sep 16 '20

Wait til he learns about TeX versioning scheme.

-12

u/McBeeff Sep 16 '20

I mean, seems like you are trying to solve a problem that doesn't exist. If you start with version 3.0 , then have updates until 3.9 but you are not ready to move on to an entire new version of python, then just make 3.91. I don't see why this has to be difficult .

12

u/s3cur1ty Sep 16 '20 edited Aug 08 '24

This post has been removed.

-5

u/McBeeff Sep 16 '20

I mean I guess. Seems weird to do it that way. What makes it Proper?

6

u/s3cur1ty Sep 16 '20 edited Aug 08 '24

This post has been removed.

3

u/[deleted] Sep 17 '20

Seems weird to do it that way

You want to count 1, 2, 3... 9, 91, 92, 93... and you think we are the weird ones?

5

u/Sw429 Sep 16 '20

You shouldn't look at it like decimals. It should be read as "major version 3, minor version 9" instead of "version 3.9".

2

u/BelieveBees Sep 17 '20

How would jumping from 9 to 91 be less difficult / confusing? You would also run into this “3.99 -> 3.991”.

9

u/PirateNinjasReddit Pythonista Sep 16 '20

What of we do a hundred or so releases of python 3? I.e. 3.420.69 could be a valid release.

6

u/Hamster_S_Thompson Sep 16 '20

That's what the dots are for. You never know how many versions there will be

2

u/NoLongerUsableName import pythonSkills Sep 16 '20

Would create confusion with Python 3.0 bugfix updates like 3.0.1.

1

u/flying-sheep Sep 16 '20

Versions are interpreted similarly to tuple(int(segment) for segment in version_string.split('.'))

They are not floats.