News for hackers. Stuff that matters.
Re:Why do we need Flask, Celery, and Redis? (2019) by antoinealb on Saturday April 18, 2020 @11:14AM (#22908283)
To nuance your comment, you can still get some form of parallelism, "just not" thread parallelism in Python. You can still spawn multiple handler process, or have threaded code in a C extension.
Re:Why do we need Flask, Celery, and Redis? (2019) by eloff on Saturday April 18, 2020 @12:40PM (#22908881)
Yes, you can use multiple processes to get the parallelism. But that's quite limiting compared with goroutines. Passing data back and forth is hard, and you can petty much forget about shared data structures. Memory usage is also much higher.
Re:Why do we need Flask, Celery, and Redis? (2019) by zepto on Saturday April 18, 2020 @11:35AM (#22908421)
It’s arguable whether either of those are ‘in python’.
Re:Why do we need Flask, Celery, and Redis? (2019) by quacker on Saturday April 18, 2020 @11:50AM (#22908518)
The multiprocessing module in the standard library is absolutely a Python-native way to do parallelism:

    with Pool(5) as p:
        print(p.map(f, [1, 2, 3]))
This runs f(1), f(2), and f(3) in parallel, using a pool of five processes.

https://docs.python.org/3.6/library/multiprocessing.html

Re:Why do we need Flask, Celery, and Redis? (2019) by goostavos on Saturday April 18, 2020 @12:51PM (#22908995)
Whoa! It never occurred to me that `Pool` could be used with context manager. I've always typed out `.close()` manually like a sucker.
Re:Why do we need Flask, Celery, and Redis? (2019) by kbutler on Saturday April 18, 2020 @11:59AM (#22908567)
https://docs.python.org/2/library/multiprocessing.html

Python standard library since 2.6. Pretty much the definition of "in python".