Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #45629 > unrolled thread
| Started by | Fábio Santos <fabiosantosart@gmail.com> |
|---|---|
| First post | 2013-05-20 19:04 +0100 |
| Last post | 2013-05-20 19:04 +0100 |
| 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.
Re: Please help with Threading Fábio Santos <fabiosantosart@gmail.com> - 2013-05-20 19:04 +0100
| From | Fábio Santos <fabiosantosart@gmail.com> |
|---|---|
| Date | 2013-05-20 19:04 +0100 |
| Subject | Re: Please help with Threading |
| Message-ID | <mailman.1893.1369073094.3114.python-list@python.org> |
[Multipart message — attachments visible in raw view] — view raw
I didn't know that. On 20 May 2013 12:10, "Dave Angel" <davea@davea.name> wrote: > Are you making function calls, using system libraries, or creating or deleting any objects? All of these use the GIL because they use common data structures shared among all threads. At the lowest level, creating an object requires locked access to the memory manager. > > > Don't forget, the GIL gets used much more for Python internals than it does for the visible stuff. I did not know that. It's both interesting and somehow obvious, although I didn't know it yet.
Back to top | Article view | comp.lang.python
csiph-web