Re: [C++-sig] Wrapper for bytes type?

boost.python should definitely have things like that. Until then, you might check out ackward: http://code.google.com/p/ackward/ The ackward::core library has wrappers for bytes and bytearray (among other things.) Austin On Sun, Jun 26, 2011 at 6:37 PM, Andreas Kloeckner wrote: > Hi there, >

Re: [C++-sig] boost python exception handling

Hi Ryan, I tried out your code (g++, python2.6, boost-1.40) and it worked just fine. However, I had to make a few changes to your compilation command to get it working. The python module you're defining is called "testing", but your command is generating a "libclassical.so"; you need to output "te

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

correct "__name__" now. Austin On Mon, Dec 20, 2010 at 4:04 PM, Austin Bingham wrote: > 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, som

Re: [C++-sig] builtin_converters.hpp using outdated API on win64 builds

> OK, I'll check in your suggested change. Great, I see it in the trunk now. Thanks! Austin ___ Cplusplus-sig mailing list Cplusplus-sig@python.org http://mail.python.org/mailman/listinfo/cplusplus-sig

Re: [C++-sig] builtin_converters.hpp using outdated API on win64 builds

On Thu, Dec 23, 2010 at 12:49 PM, Ralf W. Grosse-Kunstleve wrote: > - Original Message > >> I'm currently trying to build boost-1.45 against python-3.1.3 on  win64 >> (visual studio 2009 sp1). This build is failing  because >> boost/python/converter/builtin_converters.hpp is using APIs th

[C++-sig] builtin_converters.hpp using outdated API on win64 builds

I'm currently trying to build boost-1.45 against python-3.1.3 on win64 (visual studio 2009 sp1). This build is failing because boost/python/converter/builtin_converters.hpp is using APIs that have been removed from python3 without checking the python version; at lines 138 and 144 PyInt_FromLong is

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

I think so...I saw a 2to3 being executed when I tried running the regression tests, at least. Austin On Tue, Dec 21, 2010 at 9:21 AM, Ralf W. Grosse-Kunstleve wrote: >> I'm testing  release branch against python 3 (see Trigve in > >> http://www.boost.org/development/tests/release/developer/summa

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

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

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

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.

[C++-sig] Catching Boost.Python.ArgumentError

I feel like I'm missing something simple, but how do I catch Boost.Python.ArgumentException? As far as I can tell, the Boost.Python module is not something I can import explicitly, so I can't write "catch Boost.Python.ArgumentException:". I can do something like comparing type and module name strin

Re: [C++-sig] boost python to/from python type conversion

If it's any help, I wrote a small bit on the details of writing converters. It might help clarify some of the mechanics which, I agree, are a bit mysterious: http://misspent.wordpress.com/2009/09/27/how-to-write-boost-python-converters/ Austin On Wed, Sep 30, 2009 at 11:40 PM, James Amundson

Re: [C++-sig] Fwd: [boost-python] Making a reference to the PyObject* in construct()

Austin On Sat, Sep 26, 2009 at 6:07 PM, troy d. straszheim wrote: > Austin Bingham wrote: >> >> I can't find any documentation re: the "borrowed" nature of obj_ptr, >> so I really just assumed that it was a normal, pre-incremented >> reference. Any help

[C++-sig] Fwd: [boost-python] Making a reference to the PyObject* in construct()

y just assumed that it was a normal, pre-incremented reference. Any help on this would be great. Thanks. Austin Bingham ___ Cplusplus-sig mailing list Cplusplus-sig@python.org http://mail.python.org/mailman/listinfo/cplusplus-sig