←back to thread

The first year of free-threaded Python

(labs.quansight.org)
291 points rbanffy | 1 comments | 16 May 25 09:42 UTC | HN request time: 0.211s | source
Show context
AlexanderDhoore ◴[16 May 25 11:03 UTC] No.44003888[source]▶
Am I the only one who sort of fears the day when Python loses the GIL? I don't think Python developers know what they’re asking for. I don't really trust complex multithreaded code in any language. Python, with its dynamic nature, I trust least of all.
replies(19): >>44003924 #>>44003936 #>>44003940 #>>44003943 #>>44003945 #>>44003958 #>>44003971 #>>44004203 #>>44004251 #>>44004431 #>>44004501 #>>44005012 #>>44005100 #>>44005259 #>>44005773 #>>44006165 #>>44007388 #>>44011009 #>>44011917 #
miohtama ◴[16 May 25 11:13 UTC] No.44003943[source]▶
GIL or no-GIL concerns only people who want to run multicore workloads. If you are not already spending time threading or multiprocessing your code there is practically no change. Most race condition issues which you need to think are there regardless of GIL.
replies(3): >>44004241 #>>44005583 #>>44011886 #
1. monkeyelite ◴[17 May 25 03:44 UTC] No.44011886[source]▶
When you launch processes to do work you get multi-core workload balancing for free.