15,000 lines of verified cryptography now in Python

Re:15,000 lines of verified cryptography now in Python by sitkack on Saturday April 19, 2025 @09:40AM (#43736328)

I have been getting paid to write Python since the late 90s and it amazes me how it consistently has these needless own goals, yet still keeps on going in spite of itself. Way to go Python!

spaCy should make Cython optional

hard fork Cython to not used stringitized annotations

stay on Python 3.12 forever and then skip to 3.15

It is like have a crowd of people trying to outdo each other on how much self harm they can induce.

[ Parent | on HN ]

Re:15,000 lines of verified cryptography now in Python by ChrisMarshallNY on Saturday April 19, 2025 @09:44AM (#43736349)

> It is like have a crowd of people trying to outdo each other on how much self harm they can induce.

See: Lemmings[0]

[0] https://en.wikipedia.org/wiki/Lemmings_(National_Lampoon)

[ Parent | on HN ]

Re:15,000 lines of verified cryptography now in Python by sitkack on Saturday April 19, 2025 @12:16PM (#43737375)

I am picturing a whole dis track at pycon where we creatively mock everything and everyone.

[ Parent | on HN ]

Re:15,000 lines of verified cryptography now in Python by martinky24 on Saturday April 19, 2025 @09:51AM (#43736408)

What exactly is the own goal here…? They’re making the language better in the upcoming release. This is how normal software works.

In no world is this an “own goal”. God forbid they take on a big task for the betterment of the future language.

[ Parent | on HN ]

Re:15,000 lines of verified cryptography now in Python by sitkack on Saturday April 19, 2025 @12:12PM (#43737354)

I don’t think you understand the whole issue of why spaCy can’t move to Python 3.13

God forbid.

[ Parent | on HN ]

Re:15,000 lines of verified cryptography now in Python by yjftsjthsd-h on Saturday April 19, 2025 @02:47PM (#43738516)

> What exactly is the own goal here…? They’re making the language better in the upcoming release. This is how normal software works.

Backward incompatible changes are an own goal because they either (depending on your view) make the software worse, or make it better and then make those improvements unavailable to users.

[ Parent | on HN ]