r/Python • • Sep 15 '20

Resource Python 3.9: All You need to know 👊

https://ayushi7rawat.hashnode.dev/python-39-all-you-need-to-know
1.2k Upvotes

204 comments sorted by

View all comments

12

u/productive_guy123 Sep 15 '20

Crazy how some companies are on python 2.0 while we're so close to 4.0

0

u/[deleted] Sep 15 '20

[deleted]

2

u/PeridexisErrant Sep 16 '20

And you can use flake8-2020 to check for uses of sys.version or sys.version_info that will break with a two-digit minor version!

53

u/Bahet Sep 15 '20

I don’t think there’s been any confirmation of Python 4

48

u/[deleted] Sep 15 '20 edited Jun 20 '23

Unfortunately Reddit has choosen the path of corporate greed. This is no longer a user based forum but a emotionless money machine. Good buy redditors. -- mass edited with https://redact.dev/

12

u/productive_guy123 Sep 15 '20

Ahh, misunderstood the release transition thanks

18

u/kankyo Sep 15 '20

Afaik the plan is to go to 4.0 just to trigger the removal of the deprecated stuff that is scheduled for 4.0. So it can really happen at any time when the core devs feel like it. There will be no big disruption.

0

u/[deleted] Sep 15 '20

[deleted]

9

u/kankyo Sep 15 '20

There are depreciation warnings in python NOW about 4.0. It's happening. It's just going to be a non-event, the way it should be.

1

u/Mezzomaniac Sep 16 '20

I haven’t come across those deprecation warnings. What do they relate to?

2

u/kankyo Sep 16 '20

Hmm... Seems like they've changed them so now they are about python 3.10. I am not a fan of that. https://www.python.org/dev/peps/pep-0563/

→ More replies (2)

4

u/toyg Sep 15 '20

there is no substantial language change that would justify rewrites to an incompatible python version

4.0 will likely NOT be an incompatible version at all. Nobody wants to repeat 3.0. The most they’ll do is removing long-deprecated features. Code that runs “4.0 - 0.1” will work fine on 4.0, whenever that comes.

31

u/[deleted] Sep 15 '20

None of my customers are on 2.x anymore. I make it a requirement that they upgrade to 3.x and I do not write them anything in 2.x compatibility syntax. I'm doing my part to help fix the world one server at a time.

11

u/[deleted] Sep 15 '20

You’re doing God’s work thank you. I’m in academia and it has been a nightmare. I force everyone I work with to be in python 3. I will not budge, nor accept absolutely anything in python 2.

→ More replies (6)

5

u/sdf_iain Sep 15 '20 edited Sep 15 '20

Python uses does not use semantic versioning, but rather it’s own versioning scheme (assuming I’m reading that PEP right, it’s written to be broadly applicable).

However, the same point stands numbering in any particular spot may exceed ten (I.e. 0.11.13) without automatically incrementing any other section.

EDIT: assumptions changed to be, hopefully, more accurate

9

u/bakery2k Sep 15 '20 edited Sep 15 '20

Python uses semantic versioning

Not exactly. Minor releases often contain some breaking changes.

2

u/[deleted] Sep 15 '20

Basically every project in the history of the world that “adheres to semver”

1

u/muntoo R_{μν} - 1/2 R g_{μν} + Λ g_{μν} = 8π T_{μν} Sep 16 '20

That's because semantic versioning is way too idealistic. It equates all breaking changes to each other. But some breaking changes are much more significant than others. (57 -> 58): dropped support for x86 might be a much more significant change than (56 -> 57): dropped support for Z80 but they look almost the same as each other from the version numbering.

2

u/[deleted] Sep 15 '20

[Citation needed]

→ More replies (5)

1

u/proverbialbunny Data Scientist Sep 16 '20

Really? Isn't Python 2 officially EOL at this point? Many services have stopped supporting it recently. If companies do not upgrade they'll find themselves in the Isles of Legacy. (Which I just made up.)