Python adopts a 12-month release cycle

Re:Python adopts a 12-month release cycle by mikepurvis on Friday November 01, 2019 @12:53PM (#21420956)

I think there's also an effect where some of us have gotten used to Python 2.7.x being utterly predictable and unchanging for like, the decade since it came out.

It's not Python's fault, but for example I was trying to get something running on Ubuntu 16.04 (Python 3.5) where the primary developer of it is running Ubuntu 18.04 (Python 3.6), and it seems like 3.5's version of the asyncio module has a bunch of bugs that make the tool in question basically unusable.

I know the usual advice— install newer Python from deadsnakes, use a virtualenv, etc. None of this stuff is the end of the world, but it can be jarring if you're only now getting off the Python 2.7 train and used to everything just working everywhere.

[ Parent | on HN ]

Re:Python adopts a 12-month release cycle by kstrauser on Friday November 01, 2019 @01:17PM (#21421298)

That's not really fair, though. If the developer were writing it on 2.7 and you were running it on 2.6, I wouldn't hold that against Python 2.

[ Parent | on HN ]

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

Oh I completely acknowledge that. This is less about Python and more "fast moving platform" vs "slow moving platform".

[ Parent | on HN ]

Re:Python adopts a 12-month release cycle by takeda on Friday November 01, 2019 @03:05PM (#21422574)

well asyncio was introduced in 3.5 though, it just happened that initial version was buggy and you should assume asyncio is available since 3.6 (or actually 3.5.3+)

[ Parent | on HN ]