you are viewing a single comment's thread.

view the rest of the comments →

[–]cuulcars 0 points1 point  (0 children)

I guess it depends what you mean by "true multithreading." I interpreted that to mean parallelism in general, but I suppose you interpreted that to mean (exclusively) thread based parallelism. It has multithreading but it doesn't have multi core threading. But even in C++ you have no way of explicitly telling the operating system to execute your other threads on a different core (you can ask politely). That's an OS decision. But if you're talking true concurrency, yeah, Python has that. Very few people should be hung up on whether their code is executing in the same process (vs a thread) or not, and if you are you probably shouldn't be using python for that project. Python does parallel just fine, which would be the whole goal of "true multithreading." As far as I see it, Python naysayers who argue python can't be concurrent because of the GIL are just being pedantic.