Jim,
My answer for 1), 2) for module specific behavior would be that I
would probably not use module specific behavior. In my current project
I separate the code into multiple BOOST_PYTHON_MODULE. So I would want
to use project specific behavior and not behavior specific to the
BOOST_PYTHON_MODULE
I'd like to restart the discussion on how conversions will work in
Boost.Python v3. Here's the starting point:
I'd like to see support for static, template-based conversions. These
would be defined by [partial-]specializing a traits class, and I tend to
think they should only be invoked afte
To summarize how I'm approaching this now:
- I think the cmake/github Boost repositories look like the right place
to put this.
- I'm going to spend some time digesting the langbinding and luabind
code, and try to put together a skeleton package; when it gets mature
enough for others to find
on Sat Sep 17 2011, Ravi wrote:
> On Friday 26 August 2011 16:39:11 Jim Bosch wrote:
>> > Well, speaking for myself, mostly time. I'd be inclined to do a rewrite
>
>> > along the lines of the langbinding ideas if I had time.
>>
>> I had only been vaguely aware of langbinding until I followed u
