Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #46526 > unrolled thread

Re: Python and GIL

Started byChris Angelico <rosuav@gmail.com>
First post2013-05-31 04:30 +1000
Last post2013-05-31 04:30 +1000
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Python and GIL Chris Angelico <rosuav@gmail.com> - 2013-05-31 04:30 +1000

#46526 — Re: Python and GIL

FromChris Angelico <rosuav@gmail.com>
Date2013-05-31 04:30 +1000
SubjectRe: Python and GIL
Message-ID<mailman.2442.1369938658.3114.python-list@python.org>
On Fri, May 31, 2013 at 4:14 AM, Ana Marija Sokovic
<sokovic.anamarija@gmail.com> wrote:
> Hi,
>
> Can somebody explain to me how would you proceed in releasing the GIL and
> whether you think it will have consequences?

You release the GIL in C-level code when you don't need to work with
Python objects for a while. Simple example is when you need to wait
for something - for instance, if you attempt to read from a pipe, you
can release the GIL before reading, then reacquire it afterward. The
consequence is that you can't do anything with Python objects till you
reacquire it. It's like any other resource-guarding mutex lock.

ChrisA

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web