Issue 6269: threading documentation makes no mention of the GIL (original) (raw)

Issue6269

Created on 2009-06-11 20:37 by segfaulthunter, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (5)
msg89259 - (view)	Author: Florian Mayer (segfaulthunter)	Date: 2009-06-11 20:37
I think the GIL should be mentioned in the threading documentation, so that people do not try to use them for scalability reasons.
msg89838 - (view)	Author: Jesse Noller (jnoller) *	Date: 2009-06-29 13:52
I strongly disagree with the wording of the patch as-is. It makes no mention of the simple fact that I/O blocked threads get a benefit with threading, and so on. I do agree with adding some details about this in the core documentation however.
msg93003 - (view)	Author: Rene Dudfield (illume)	Date: 2009-09-22 16:33
hello, CPU intensive programs can also benefit from the GIL if they use code which releases the GIL around the CPU intensive parts. Some parts of python do this, as do the numpy and pygame extensions amongst others. Another good, but separate, documentation patch would be to document which functions release the GIL. cheers,
msg119597 - (view)	Author: ysj.ray (ysj.ray)	Date: 2010-10-26 10:06
Agree with Jesse, the description in the patch is not quite correct. I think detailed description of the GIL has been given in C API documentation: http://docs.python.org/c-api/init.html#thread-state-and-the-global-interpreter-lock. How about just give this link in threading module documentation?
msg125564 - (view)	Author: Antoine Pitrou (pitrou) *	Date: 2011-01-06 16:40
Ok, done in r87792, r87793 and r87794, thank you.