[issue6269] threading documentation makes no mention of the GIL

Antoine Pitrou added the comment: Ok, done in r87792, r87793 and r87794, thank you. -- nosy: +pitrou resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___

[issue6269] threading documentation makes no mention of the GIL

Changes by Senthil Kumaran : -- nosy: +orsenthil ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue6269] threading documentation makes no mention of the GIL

Ray.Allen added the comment: 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 i

[issue6269] threading documentation makes no mention of the GIL

Changes by Antoine Pitrou : -- assignee: nobody -> d...@python nosy: +d...@python versions: +Python 3.1, Python 3.2 ___ Python tracker ___

[issue6269] threading documentation makes no mention of the GIL

Changes by Jesse Noller : -- assignee: jnoller -> nobody keywords: +easy nosy: +nobody priority: normal -> low ___ Python tracker ___ _

[issue6269] threading documentation makes no mention of the GIL

Rene Dudfield added the comment: 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 pa

[issue6269] threading documentation makes no mention of the GIL

Changes by Georg Brandl : -- assignee: georg.brandl -> jnoller ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue6269] threading documentation makes no mention of the GIL

Jesse Noller added the comment: 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. -- nosy

[issue6269] threading documentation makes no mention of the GIL

New submission from Florian Mayer : I think the GIL should be mentioned in the threading documentation, so that people do not try to use them for scalability reasons. -- assignee: georg.brandl components: Documentation files: threading.rst.patch keywords: patch messages: 89259 nosy: geor