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 takeda on Friday November 01, 2019 @01:31PM (#21421464)
That's not because 3.8 broke something. The packages you mentioned require compiling. To make it simpler for users, the maintainers also provide precompiled versions. The issue here is that no one precompiled them for 3.8 yet. You can still install them but you need to have compiler and their dependencies installed.

The length of release cycle is irrelevant for this particular problem.

[ Parent | on HN ]
Re:Python adopts a 12-month release cycle by icegreentea2 on Friday November 01, 2019 @01:40PM (#21421623)
Those packages do need re-compiling, but the official recompiles are blocked by breakages in 3.8.

One of the issues blocking scipy release is a bug in 3.8's multiprocessing library: https://bugs.python.org/issue38501

Technically they could probably patch around that in their test-suite... but it really is regression in the language.

[ Parent | on HN ]
Re:Python adopts a 12-month release cycle by takeda on Friday November 01, 2019 @02:51PM (#21422429)
I see, I wasn't aware of that, my bad.
[ Parent | on HN ]
Re:Python adopts a 12-month release cycle by kissgyorgy on Friday November 01, 2019 @01:39PM (#21421602)
> The length of release cycle is irrelevant for this particular problem.

No because you need to compile those packages more often, which as it seem, very problematic.

[ Parent | on HN ]