News for hackers. Stuff that matters.

A comment on Python adopts a 12-month release cycle. Parent comment

Re:Python adopts a 12-month release cycle by icegreentea2 on Friday November 01, 2019 @02:24PM (#21422139)
It's your call to make. If your system doesn't have some sort of 'security' risk to it, then all the reasons you have to upgrade are purely internal cost-benefit analysis.

Code is a tool, treat it like any other. Just be aware of possible accumulating deferred costs. I don't know exactly what field your in, but just imagine any other piece of equipment or component going EOL, and the manufacturer only providing semi-drop in replacements. Or even if they are advertised as "drop in", you know that half the time they aren't, and something derpy happens on integration.

[ Parent | on HN ]
Re:Python adopts a 12-month release cycle by willis936 on Friday November 01, 2019 @05:24PM (#21423852)
The system is not firewalled from the internet. There are tools that need internet based licenses. There are organization firewalls, but there is always a risk involved with having unpatched platforms. I have to weigh that risk against the cost of porting. Both are difficult to gauge.
[ Parent | on HN ]
Re:Python adopts a 12-month release cycle by icegreentea2 on Friday November 01, 2019 @05:50PM (#21424066)
How are the Python 2.5 components being invoked? Are they python processes that are constantly running? Or are they jobs spun up by other processes?
[ Parent | on HN ]
Re:Python adopts a 12-month release cycle by willis936 on Saturday November 02, 2019 @01:42AM (#21426095)
Oh they’re always running and on dozens of machines.
[ Parent | on HN ]