this post was submitted on 13 Jul 2024
113 points (98.3% liked)

Programming

17651 readers
316 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] csm10495 28 points 5 months ago (1 children)

It's exciting, but man there are lots of assumptions in native python built around the gil.

I've seen lists, etc. modified by threads assuming the gil locks for them. Testing this e2e for any production deployment can be a bit of a nightmare.

[–] [email protected] 40 points 5 months ago* (last edited 5 months ago) (3 children)

My company makes it super easy for me - we're just going to continue on python 2.7 and add this to the long list of reasons why we're not upgrading.

Please send help.

[–] [email protected] 3 points 5 months ago (1 children)

You may be pleased to know that PyPy's Python 2.7 branch will be maintained indefinitely, since PyPy is also written in Python 2.7. Also, if you can't leave CPython yet, ActivePython's team is publishing CPython 2.7 security patches.

[–] [email protected] 3 points 5 months ago

We already have contracts in place to get security patches. That's usually the InfoSec team's problem anyway.

As a developer, my life gets hard due to library support. We manage internal forks of multiple open source projects just to make them python 2 compatible. A non-trivial amount of time is wasted on this, and we don't even have it available for public use. 🤷‍♂️

[–] [email protected] 2 points 5 months ago (2 children)

Why would you not be upgrading due to a new feature of python? You don't like new features or was that a badly wordered sentence?

[–] [email protected] 10 points 5 months ago

Because using an exceedingly insecure version is cheaper until an inevitable compromise makes it expensive.

[–] [email protected] 4 points 5 months ago

More work, more debt. The more debt you have the harder it is to let go.

[–] [email protected] 2 points 5 months ago

Python 2.7 and iOS mobile programmers stuck on Objective-C could start a support group.