On 16/12/2012 22:58, Adam Preble wrote:
Is the particular focus of your code on getting the GIL released during
longer method invocations? I don't have any sway with Boost or
anything, so I'm just asking out of my own personal curiosities. When I
first saw the message, without seeing the code,
On 17/12/2012 03:25, Niall Douglas wrote:
I won't go into too much detail here (search this list's archives),
but in short there isn't just GIL management but also interpreter
management, and on top of that both of those have to work right as
exception throws happen plus policies must be institut
On 25 Dec 2012 at 12:14, John Zwinck wrote:
> The code I published is agnostic about iterators and iteration--the user
> must explicitly decide when the GIL is to be released and reacquired.
> I'm sure there could be fancier ways of doing it, e.g. with tags given
> to BPL's class_::def() for lo
For a BPL wrapped object to be a python string, it simply needs to
provide the same API as a Python string.
Replicate the magic underscore methods of python's string object and
your wrapped std::string becomes a python string.
It used to be the case that inheriting your BPL object from python's
