On 03/08/2018 05:06 PM, Lawrence D’Oliveiro wrote:
On Friday, March 9, 2018 at 11:43:00 AM UTC+13, Paul Rubin wrote:
That you're using threading.Lock for something like this is a borderline
code smell.
Any use of multithreading in non-CPU-intensive code is a code smell.
But CPU intensive code is exactly the circumstance where Python
threading lets you down. It really shines when you're I/O-bound.
--
Rob Gaddi, Highland Technology -- www.highlandtechnology.com
Email address domain is currently out of order. See above to fix.
--
https://mail.python.org/mailman/listinfo/python-list
