Python adopts a 12-month release cycle

Re:Python adopts a 12-month release cycle by AlexeyBrin on Friday November 01, 2019 @12:45PM (#21420831)

This is great if you code in pure Python! The problem is that every new Python version seems to break something. Python 3.8 was released almost two weeks ago, and some popular libraries still don't work with it, e. g. SciPy, Matplotlib, OpenCV, PyQt, PySide2 and probably a bunch of other libraries that depend on the above.

[ Parent | on HN ]

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 ]

Re:Python adopts a 12-month release cycle by ddavis on Friday November 01, 2019 @01:33PM (#21421499)

Binary wheels aren't out from everyone you mentioned yet (they are for NumPy and SciPy... but the maintainers of most of the packages you mention appear to usually wait for their next releases before getting the wheels out), but a NumPy + SciPy + Matplotlib + Pandas + Scikit-learn setup was functional before 3.8.0 was released (I had one spinning during the betas, one just has to be willing to compile things from source usually).

[ Parent | on HN ]

Re:Python adopts a 12-month release cycle by AlexeyBrin on Friday November 01, 2019 @01:45PM (#21421669)

> Binary wheels aren't out from everyone you mentioned yet (they are for NumPy and SciPy...

https://pypi.org/project/scipy/#files sorry, there is no 3.8 binary wheel for SciPy.

[ Parent | on HN ]

Re:Python adopts a 12-month release cycle by ddavis on Friday November 01, 2019 @04:43PM (#21423499)

You're right, I mixed up scipy and pandas.

[ Parent | on HN ]

Re:Python adopts a 12-month release cycle by progval on Friday November 01, 2019 @01:27PM (#21421419)

According to the announcement, it should get better: "Now that the stable ABI has been cleaned, extension modules should feel more comfortable targeting the stable ABI which should make supporting newer versions of Python much easier"

[ Parent | on HN ]

Re:Python adopts a 12-month release cycle by maxerickson on Friday November 01, 2019 @12:49PM (#21420892)

There is work towards a stable abi, that should help with such things, eventually.

[ Parent | on HN ]

Re:Python adopts a 12-month release cycle by dannyz on Friday November 01, 2019 @01:07PM (#21421136)

Yes, exactly. Every new 3.x release ends up being a not insignificant amount of work for us to update our build system for our not pure Python packages.

[ Parent | on HN ]

Re:Python adopts a 12-month release cycle by dsd on Friday November 01, 2019 @01:08PM (#21421154)

Maybe a faster release cycle will help Python and friends insulate from this issue better. Akin to os security updates.

[ Parent | on HN ]