News for hackers. Stuff that matters.
Re:Concurrency with Python: Threads and Locks by heavenlyblue on Thursday March 21, 2019 @08:01AM (#19451278)
So technically if you wrote most of your number-crunching code as a C module for python, then you could use threads...

Can't you see a problem here?

Re:Concurrency with Python: Threads and Locks by dagw on Thursday March 21, 2019 @08:19AM (#19451435)
If you don't want to use C (I don't blame you if you don't) you could use Cython or Numba. And certainly in my number crunching code the amount of code that actually crunches numbers, and thus could really benefit from being written in a GIL releasing way, is really quite small.
Re:Concurrency with Python: Threads and Locks by chrisseaton on Thursday March 21, 2019 @08:16AM (#19451412)
No you can still use pure Python, and use multiple threads, and get concurrency just fine. The global lock doesn't stop you doing that! C extensions being able to release the lock is just a bonus on top.
Re:Concurrency with Python: Threads and Locks by objectified on Thursday March 21, 2019 @08:34AM (#19451550)
Lots of problems are merely I/O related, which can be solved just fine with Python threads. As for number crunching (let's assume that means CPU intensive tasks), you can always still resort to multiprocessing (which can also be combined with multithreading, I fail to see why such paradigms cannot be combined).
Re:Concurrency with Python: Threads and Locks by heavenlyblue on Thursday March 21, 2019 @12:31PM (#19454224)
Well, io-related problems can be solved even better by using gevent.

The io-related problems I had with paramiko, on the other hand - last time I checked could neither be solved with threads or gevent.

So that’s a weak point to be made anyway.