Jump to ratings and reviews
Rate this book

Python Parallel Programming Cookbook: Over 70 recipes to solve challenges in multithreading and distributed system with Python 3, 2nd Edition

Rate this book
Python Parallel Programming Cookbook

370 pages, paperback

Published September 6, 2019

2 people are currently reading
7 people want to read

About the author

Ratings & Reviews

What do you think?
Rate this book

Friends & Following

Create a free account to discover what your friends think of this book!

Community Reviews

5 stars
0 (0%)
4 stars
4 (66%)
3 stars
1 (16%)
2 stars
1 (16%)
1 star
0 (0%)
Displaying 1 - 2 of 2 reviews
1 review
November 2, 2020
Nice introduction to the possibilities that Python awards in terms of parallel and concurrent programming. Do not expect a lot of detail into any one technique, but provides a lot of references for getting deep into any of the packages if needed.
Profile Image for Alex.
5 reviews
April 26, 2020
My opinion: A very basic introductory book on various aspects of parallel programming as multithreading, multiprocessing and some CUDA stuff. Each module gets a description and some primitive examples, which you can alternatively read for free in the corresponding library documentations.

Conclusion: I do not recommend this book to advanced developers, because it is super introductory. I could not recommend this book to beginners either, because it has a lot of information that beginners do not need. If you are interested in select topics of the book you would be better off reading documentation.

Note: if you are interested in CUDA you should be familiar with C.


Other thoughts: I noticed quite a few misconceptions and small errors in this book, for example:

- on p.42 the author is claiming that he is changing an instance variable with `first_instance.common_value = 1500`. However, he is essentially creating a shadowing instance variable to the `common_value` class variable with the same name. That is a common pitfall and you can read more about it in "Class vs Instance Variable Pitfalls" section in Python Tricks by Dan Bader;

- on p.48 the author is suggesting to import everything from a library with `from do_something import *`, which is a bad practice. Any decent literature would suggest against importing everything from a library/module because possible namespace confusions. It would be much clearer to import all the required elements explicitly one by one (PEP 328).
Displaying 1 - 2 of 2 reviews

Can't find what you're looking for?

Get help and learn more about the design.