[C++-sig] Am I crazy or is it my computer?

[Ralf W. Grosse-Kunstleve]

I don't know too much about threading, but I think

- you still need Niall Douglas' patches
if your threads want
  to call back into Python
- it is fair to say that the real problem is "Python & threading",

  mainly because of the dreaded global interpreter lock (GIL)

Recently there has been some discussion on python-dev about getting

rid of the GIL, but I'm not holding my breath...


IIUC, if your threads never call back into Python you don't have to

deal with the GIL.
If you have to deal with the GIL I'm not surprised to see you
frustrated. This is something that was largely ignored in the
Boost.Python development (there is only so much you can hope to
achieve in a given amount of time...).



In my work I've consciously avoided threading. Under this simplification
I find Boost.Python well documented and intuitive :-)

Ralf



----- Original Message ----

From: Matthew Scouten <matthew.scouten at gmail.com>

To: Development of Python/C++ integration <C++-sig at python.org>

Sent: Wednesday, October 31, 2007 1:11:27 PM

Subject: Re: [C++-sig] Am I crazy or is it my computer?



 Ok, I just found this: http://www.boost.org/libs/python/doc/v2/faq.html#threadsupport



I seems to be saying that I can not do what I want with out patching Boost::Python (or does this only apply to multiple interpretors? ) 

Is this still true (please tell me it's been fixed)?

if so, where can I get this patch and how do I apply it?



I asked about multi-threading and boost python in on this list a while ago, and got no answer. I took this a a "go ahead, no problems". If I am being an idiot, could you tell me so? Just flame away at me so I know I've been stupid.  A lot of people here actually know what they are doing. I do not have that luxury.  I am finding boost python extremely complex and non-intuitive.  There is also a lack of good documentation (example code is nice to have, but does not constitute proper documentation all by itself).