Python 3.11 whack-a-mole

RypPn

RypPn

No-one can have failed to notice python311 being in an eternal state of security vulnerabilities for quite a while now as the devs try to backport patches. Considering 3.11 will probably reach EOL before the dust settles,

https://devguide.python.org/versions/

wouldn't it be more sane to move on to 3.14?
 
I thought it was the lang/cython vs lang/cython0...
😲

Sometimes, ports specify that they depend on cython3, sometimes on cython 0.29... I can't tell if they are interchangeable or not, but they do conflict in the FreeBSD pkg installation database. It's either try to unset the knob that specifies the Cython dependency, or uninstall the offending package that conflicts with the dependency (and risk running into dependency hell if you do it wrong. The right way to do that is with make deinstall, which only applies if you compile the ports from ground up like I do. If you use packages, good luck.)
😒
 
I probly wouldn't stage anything written in python anywhere where security is an issue so it's a moot point to me. I do lots of rapid app prototyping in python and the switch from prototype to deployable code would be a rewrite in c++.

Sorry, I know this doesn't directly contribute to answering your question, but I guess my point is that python probly shouldn't be thought of as a "secure" language in the first place.
 
You must log in or register to reply here.
Back
Top