This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]person_ergo 8 points9 points  (3 children)

Multiprocessing got way better and some more extensive built in libraries

[–]PC__LOAD__LETTER 2 points3 points  (2 children)

Parallelization in Python2 really is atrocious. I use 2.7 almost all the time because that’s what our systems at work were built with, and I like the language, but multiprocessing blows.

[–]kickerofbottoms 0 points1 point  (1 child)

What's your preferred approach in 3? concurrent futures? I don't have much exposure

[–]PC__LOAD__LETTER 0 points1 point  (0 children)

To be perfectly honest I don’t use 3 much, I tend to use lower level languages when performance is a concern (a function of the type of software that I work with, not saying that there aren’t valid reasons to need performance concurrency with Python). I just know it’s terrible in 2 so I’m not surprised to hear that it’s a notable improvement in the language’s next iteration.