Why Is the Migration to Python 3 Taking So Long?

Re:Why Is the Migration to Python 3 Taking So Long? by dividuum on Thursday November 14, 2019 @02:23PM (#21538472)

> The only real killer feature of Python3 is the async programming model.

I understand that this is one of the major features, but I personally never saw the appeal, given that gevent exists and in my experience works well most of the time. It also allows me to multiplex IO operations and doesn't rely on new syntax. I'm probably missing something?

[ Parent | on HN ]

Re:Why Is the Migration to Python 3 Taking So Long? by d0mine on Thursday November 14, 2019 @05:07PM (#21539995)

In gevent, any call may behave like an implicit "goto". Here's why "goto" is bad https://vorpus.org/blog/notes-on-structured-concurrency-or-g... (the link is stolen from @hermod's comment above)

[ Parent | on HN ]

Re:Why Is the Migration to Python 3 Taking So Long? by jlokier on Thursday November 14, 2019 @06:28PM (#21540682)

I think the nursery construct described in that link looks a lot like par blocks in Occam, Handel-C and XMOS XC.

[ Parent | on HN ]

Re:Why Is the Migration to Python 3 Taking So Long? by Scramblejams on Thursday November 14, 2019 @08:40PM (#21541523)

I find it much easier to reason about my async Python code when the async yield points are explicit. If every line can potentially yield to another async task, I find myself thinking long and hard about a lot of those lines.

[ Parent | on HN ]