➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author asvetlov
Recipients akira, asvetlov, docs@python, martin.panter, pitrou, r.david.murray
Date 2015-01-18.21:35:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAL3CFcX4KjpmbN9TehYKGzd5hHUH-+E1j1ivtYG5W8OtdpS+eg@mail.gmail.com>
In-reply-to <1421591996.48.0.614296960441.issue23251@psf.upfronthosting.co.za>
Content 
I'm with Antoine.

Yes, GIL is extremely important but please don't put GIL mentions everywhere.

On Sun, Jan 18, 2015 at 4:39 PM, Antoine Pitrou <report@bugs.python.org> wrote:
>
> Antoine Pitrou added the comment:
>
> Please let's stop it. Mentioning the GIL in every place in the documentation will only make people more worried and confused about something they shouldn't be confused or worried about.
>
> If you think some docs should discuss the GIL and its effect on running threads then I suggest writing a separate document (a HOWTO for example, like the Unicode HOWTO).
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue23251>
> _______________________________________
History
Date User Action Args
2015-01-18 21:35:21asvetlovsetrecipients: + asvetlov, pitrou, r.david.murray, docs@python, akira, martin.panter
2015-01-18 21:35:21asvetlovlinkissue23251 messages
2015-01-18 21:35:21asvetlovcreate