News for hackers. Stuff that matters.
Re:Key differences between Python 2.7.x and Python 3.x (2014) by gime_tree_fiddy on Sunday May 07, 2017 @08:25PM (#14288468)
Is it just me, or comparing Python's async/await to Go is misleading. As far as I know, even with async/await, Python is still not multicore.
Re:Key differences between Python 2.7.x and Python 3.x (2014) by xapata on Monday May 08, 2017 @01:21AM (#14289418)
Async IO is solving a different problem than you're complaining about. Python is effectively multicore in nearly every use case. The only trouble is there's no free lunch -- the multicore solution depends on which problem you're facing.

So, what's the issue you're facing?

Re:Key differences between Python 2.7.x and Python 3.x (2014) by stcredzero on Sunday May 07, 2017 @10:16PM (#14288818)
even with async/await, Python is still not multicore.

Even with its channels and scheduler, Go is still not as multicore as Erlang. And I say this as an avid Go user!

Re:Key differences between Python 2.7.x and Python 3.x (2014) by treehau5 on Sunday May 07, 2017 @11:42PM (#14289091)
What does something not being as multicore as something else mean?
Re:Key differences between Python 2.7.x and Python 3.x (2014) by gime_tree_fiddy on Thursday May 18, 2017 @06:15PM (#14371551)
Multicore in the sense that the underlying runtime (for the lack of a better word) scales to multiple cores. Like two threads in python cannot run in parallel (like at the same time, not like second one gets scheduled if first one waits for IO or network), the way a goroutine in Golang does.
Re:Key differences between Python 2.7.x and Python 3.x (2014) by stcredzero on Monday May 08, 2017 @10:48AM (#14291940)
It would be great if the GC was also multicore. As it is, the task of splitting up your application into multiple processes to have more GC still involves too much friction.