Re: [C++-sig] [Boost.Python v3] Planning and Logistics

2011-08-28 Thread Niall Douglas
On 27 Aug 2011 at 12:29, Dave Abrahams wrote: > In that case, if I were you, I would actually start using Git with the > modularized / CMake-ified Boost at http://github.com/boost-lib. If you do go for git, I have found repo embedded per-branch issue tracking (e.g. http://bugseverywhere.org/) to

Re: [C++-sig] [Boost.Python v3] Features and Scope

2011-08-28 Thread Jim Bosch
On 08/27/2011 02:08 PM, Stefan Seefeld wrote: On 08/27/2011 04:40 PM, Dave Abrahams wrote: Hmm. I'm guessing the global type registry would still be the default, and per-module registries would override these when available? It sounds like Stefan has a clear use case in mind, and I'd be curiou

Re: [C++-sig] [Boost.Python v3] Features and Scope

2011-08-28 Thread Dave Abrahams
on Sat Aug 27 2011, Stefan Seefeld wrote: > On 08/27/2011 04:40 PM, Dave Abrahams wrote: >>> Hmm. I'm guessing the global type registry would still be the >>> default, and per-module registries would override these when >>> available? It sounds like Stefan has a clear use case in mind, and >>>

Re: [C++-sig] [Boost.Python v3] Features and Scope

2011-08-28 Thread Stefan Seefeld
On 08/28/2011 02:39 PM, Dave Abrahams wrote: > on Sat Aug 27 2011, Stefan Seefeld wrote: > > >> Binding converters to particular modules (and requiring to explicitly >> import / exporting converters) seems like a solution to the above. > It might be, but your description of what you're actually pr

[C++-sig] sending a c++ class to a python function

2011-08-28 Thread Josh Stratton
I'm getting an error when I try to pass down my object that results in a seg fault. I've registered my class I'm sending down, but when I actually send it, my program exits at this line in the library right after I call the importFile() function... return call(get_managed_object(self, tag