Re: [C++-sig] Multiple calls to bp::detail::init_module() causing conflicts?

2010-12-20 Thread Trigve Siver
> From: Ralf W. Grosse-Kunstleve > To: Development of Python/C++ integration > Sent: Tue, December 21, 2010 12:48:35 AM > Subject: Re: [C++-sig] Multiple calls to bp::detail::init_module() causing >conflicts? > > Hi Austin, > Just a remark: the python3 support isn't routinely exercised. > Ove

Re: [C++-sig] Multiple calls to bp::detail::init_module() causing conflicts?

2010-12-20 Thread Austin Bingham
I'm happy to help with this, at least as my time permits. I've looked at the docs regarding the regression tests, and everything seems fairly straightforward (though I've never really wrapped my head around jam!). Is it just a question of building boost against python3, running the tests, and fixin

Re: [C++-sig] Multiple calls to bp::detail::init_module() causing conflicts?

2010-12-20 Thread Ralf W. Grosse-Kunstleve
Hi Austin, Just a remark: the python3 support isn't routinely exercised. Overlooked incompatibilities are possible. I only have time to maintain the python2 support. We need a volunteer to port the unit tests to python3. Ralf - Original Message > From: Austin Bingham > To: Development

[C++-sig] Multiple calls to bp::detail::init_module() causing conflicts?

2010-12-20 Thread Austin Bingham
I'm in the process of upgrading my project to boost-1.45.0 and python3, and I started seeing strange problems with some of my boost.python-based extension modules. Essentially, some of my modules are reporting the wrong module name, i.e. if I "print(module_object.__name__)", I get the wrong value.