Mailman 3 January 2014 - Cplusplus-sig

boost::python embedding error - runtime - Mac OS X - 1.38
by Igor Karpov Oct. 1, 2014

Oct. 1, 2014

Hi, I am trying to run the following program: #include <iostream> #include <Python.h> #include <boost/python.hpp> using namespace boost::python; using namespace std; int main(int argc, char** argv) { { // Using Python/C Py_Initialize(); PyObject* main_module = PyImport_ImportModule("__main__"); PyObject* globals = PyEval_GetGlobals(); PyObject* locals = PyEval_GetLocals(); PyRun_SimpleString("print 'Hello World, from Python/C!'\n"); Py_Finalize(); } { // Using boost::python Py_Initialize(); object main_module = import("__main__"); object main_namespace = main_module.attr("__dict__"); try { object ignored = exec("print 'Hello World, from boost::python!'\n", main_namespace); Py_Finalize(); } catch (error_already_set const& e) { PyErr_Print(); return 1; } } return 0; } on Linux (both x86 and x86_64), with Ubuntu's default version of Boost (1.34.1) installed, I am able to do so as expected: $ ./embed Hello World, from Python/C! Hello World, from boost::python! on Mac OS X, I get a runtime error: $ ./embed Hello World, from Python/C! Bus Error Running with gdb, this is the stack trace: Hello World, from Python/C! Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x00000000 0x00000000 in ?? () (gdb) where #0 0x00000000 in ?? () #1 0x00bb618f in PyEval_GetGlobals () #2 0x00bce0dd in PyImport_Import () #3 0x00bce2b0 in PyImport_ImportModule () #4 0x008127d4 in boost::python::import (name=@0xbffff4a8) at libs/python/src/import.cpp:20 #5 0x00004446 in main (argc=1, argv=0xbffff510) at embed.cc:22 For this Mac, boost version is latest (1.38) and python version is: Python 2.5.4 (r254:67917, Dec 23 2008, 14:57:27) [GCC 4.0.1 (Apple Computer, Inc. build 5363)] on darwin Is this a bug? I attached the source and the cmake file I am using to build, for convenience. Thanks, --Igor.

4 6

Re: [C++-sig] PhysX3.x Wrapping Problems
by Peter Armbrüster Jan. 30, 2014

Jan. 30, 2014

Hi Nicolay, thanks for your Tip. I tested this, but same Error. I think that is the biggest sh... Error in my live. Maybe I would better become a musician. :-) Best Regards Peter -----Ursprüngliche Nachricht----- Von: Cplusplus-sig [mailto:cplusplus-sig-bounces+arm=rfh-koeln.de@python.org] Im Auftrag von cplusplus-sig-request(a)python.org Gesendet: Mittwoch, 29. Januar 2014 16:22 An: cplusplus-sig(a)python.org Betreff: Cplusplus-sig Digest, Vol 64, Issue 12 Send Cplusplus-sig mailing list submissions to cplusplus-sig(a)python.org To subscribe or unsubscribe via the World Wide Web, visit https://mail.python.org/mailman/listinfo/cplusplus-sig or, via email, send a message with subject or body 'help' to cplusplus-sig-request(a)python.org You can reach the person managing the list at cplusplus-sig-owner(a)python.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Cplusplus-sig digest..." Today's Topics: 1. Re: Cplusplus-sig Digest, Vol 64, Issue 11 (Peter Armbr?ster) 2. Re: PhysX3.x Wrapping Problems (Nikolay Mladenov) ---------------------------------------------------------------------- Message: 1 Date: Wed, 29 Jan 2014 12:26:18 +0100 From: Peter Armbr?ster <arm(a)rfh-koeln.de> To: <cplusplus-sig(a)python.org> Subject: Re: [C++-sig] Cplusplus-sig Digest, Vol 64, Issue 11 Message-ID: <03d701cf1ce4$ee69dc30$cb3d9490$(a)rfh-koeln.de> Content-Type: text/plain; charset="iso-8859-1" Hi Niki and Giuseppe, thanks for your answers, but once I had already considered . My compiler flags are: /DWIN32 /DDEBUG /GR /RTCsu /DPX_DEBUG I wish you a nice day. Peter -----Urspr?ngliche Nachricht----- Von: Cplusplus-sig [mailto:cplusplus-sig-bounces+arm=rfh-koeln.de@python.org] Im Auftrag von cplusplus-sig-request(a)python.org Gesendet: Mittwoch, 29. Januar 2014 12:00 An: cplusplus-sig(a)python.org Betreff: Cplusplus-sig Digest, Vol 64, Issue 11 Send Cplusplus-sig mailing list submissions to cplusplus-sig(a)python.org To subscribe or unsubscribe via the World Wide Web, visit https://mail.python.org/mailman/listinfo/cplusplus-sig or, via email, send a message with subject or body 'help' to cplusplus-sig-request(a)python.org You can reach the person managing the list at cplusplus-sig-owner(a)python.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Cplusplus-sig digest..." Today's Topics: 1. Re: PhysX3.x Wrapping Problems (niki) 2. Re: PhysX3.x Wrapping Problems (Giuseppe Corbelli) ---------------------------------------------------------------------- Message: 1 Date: Wed, 29 Jan 2014 10:19:59 +0200 From: niki <niki(a)vintech.bg> To: Development of Python/C++ integration <cplusplus-sig(a)python.org> Subject: Re: [C++-sig] PhysX3.x Wrapping Problems Message-ID: <52E8B9AF.4050602(a)vintech.bg> Content-Type: text/plain; charset=UTF-8; format=flowed On 28.01.2014 18:33, Peter Armbr?ster wrote: > Dear Boost.python, C++ and Py++ Experts, > > this is my first post in your excellent Forum. > > I have chosen as the wrapper software the boost.python/Py++ Packageto > write a physx 3.x Wrapper, because I think it is the best. > > Many many thanks to David Abrahams and Roman Yakovenko for the great Tools. > > The wrapping of old versions physx 2.x had made no problems. > > And now I come across a very big problem at the 3.x Versions. > > All wrappings of classes works very well. > > The problem only exists in the PhysX free functions, which are > responsible for the initialization of PhysX. > > I try to explain with a reduced Example. > > The initialization of PhysX starts with create of foundation : > > *0 static*PxFoundation*mFoundation=NULL; > > *1 static*PxDefaultErrorCallbackgDefaultErrorCallback; > *2 static*PxDefaultAllocatorgDefaultAllocatorCallback; > 3 > mFoundation=PxCreateFoundation(PX_PHYSICS_VERSION,gDefaultAllocatorCal > lback,gDefaultErrorCallback);4 > *4 if*(!mFoundation) > > 5 fatalError("PxCreateFoundation failed!"); > > The wrapped python program generate a runtime error at line > 3:RuntimeError: Access violation - no RTTI data! Just wild guess: add compiler option to enable RTTI HTH Niki ------------------------------ Message: 2 Date: Wed, 29 Jan 2014 11:03:00 +0100 From: Giuseppe Corbelli <giuseppe.corbelli(a)copanitalia.com> To: Development of Python/C++ integration <cplusplus-sig(a)python.org> Subject: Re: [C++-sig] PhysX3.x Wrapping Problems Message-ID: <52E8D1D4.7060003(a)copanitalia.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 28/01/2014 17:33, Peter Armbr?ster wrote: > Dear Boost.python, C++ and Py++ Experts, > > this is my first post in your excellent Forum. > > I have chosen as the wrapper software the boost.python/Py++ Packageto > write a physx 3.x Wrapper, because I think it is the best. > > Many many thanks to David Abrahams and Roman Yakovenko for the great Tools. > > The wrapping of old versions physx 2.x had made no problems. > > And now I come across a very big problem at the 3.x Versions. > > All wrappings of classes works very well. > > The problem only exists in the PhysX free functions, which are > responsible for the initialization of PhysX. > > I try to explain with a reduced Example. > > The initialization of PhysX starts with create of foundation : > > *0 static*PxFoundation*mFoundation=NULL; > > *1 static*PxDefaultErrorCallbackgDefaultErrorCallback; > *2 static*PxDefaultAllocatorgDefaultAllocatorCallback; > 3 > mFoundation=PxCreateFoundation(PX_PHYSICS_VERSION,gDefaultAllocatorCal > lback,gDefaultErrorCallback);4 > *4 if*(!mFoundation) > > 5 fatalError("PxCreateFoundation failed!"); > > The wrapped python program generate a runtime error at line 3:RuntimeError: > Access violation - no RTTI data! > > Its impossible to get mFoundation. > > *Notes: * > > - physx comes as SDK: only Headers, libs and dlls. Before reading on I'd investigate the "no RTTI data" message. Make sure you're using the /GR compiler option. -- Giuseppe Corbelli WASP Software Engineer, Copan Italia S.p.A Phone: +390303666318 Fax: +390302659932 E-mail: giuseppe.corbelli(a)copanitalia.com ------------------------------ Subject: Digest Footer _______________________________________________ Cplusplus-sig mailing list Cplusplus-sig(a)python.org https://mail.python.org/mailman/listinfo/cplusplus-sig ------------------------------ End of Cplusplus-sig Digest, Vol 64, Issue 11 ********************************************* ------------------------------ Message: 2 Date: Wed, 29 Jan 2014 10:21:50 -0500 From: Nikolay Mladenov <nikolay.mladenov(a)gmail.com> To: "Development of Python/C++ integration" <cplusplus-sig(a)python.org> Subject: Re: [C++-sig] PhysX3.x Wrapping Problems Message-ID: <CACbdn-J9sPWzS4cVqB9BPnJ5A=ecz__c2qnbFoQzRtj=F0O2mw(a)mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" Recently I had such symptom - it went away when I turned "Whole Program Optimization" off On Tue, Jan 28, 2014 at 11:33 AM, Peter Armbr?ster <arm(a)rfh-koeln.de> wrote: > Dear Boost.python, C++ and Py++ Experts, > > > > this is my first post in your excellent Forum. > > > > I have chosen as the wrapper software the boost.python/Py++ Package to > write a physx 3.x Wrapper, because I think it is the best. > > Many many thanks to David Abrahams and Roman Yakovenko for the great Tools. > > > > The wrapping of old versions physx 2.x had made no problems. > > And now I come across a very big problem at the 3.x Versions. > > All wrappings of classes works very well. > > The problem only exists in the PhysX free functions, which are > responsible for the initialization of PhysX. > > > > I try to explain with a reduced Example. > > The initialization of PhysX starts with create of foundation : > > > > *0 static* PxFoundation *mFoundation = NULL; > > *1 static* PxDefaultErrorCallback gDefaultErrorCallback; > *2 static* PxDefaultAllocator gDefaultAllocatorCallback; > 3 mFoundation = PxCreateFoundation(PX_PHYSICS_VERSION, > gDefaultAllocatorCallback, gDefaultErrorCallback); 4 > *4 if*(!mFoundation) > > 5 fatalError("PxCreateFoundation failed!"); > > > > The wrapped python program generate a runtime error at line 3:RuntimeError: Access violation - no RTTI data! > > Its impossible to get mFoundation. > > > > > > > > *Notes: * > > - physx comes as SDK: only Headers, libs and dlls. > > - PxFoundation is a Abstract class: > > > > *class* PX_FOUNDATION_API PxFoundation { > *public*: > *virtual* *void* release() = 0; > *virtual* PxErrorCallback& getErrorCallback() *const* = 0; > *virtual* *void* setErrorLevel(PxErrorCode::Enum mask = > PxErrorCode::eMASK_ALL) = 0; > *virtual* PxErrorCode::Enum getErrorLevel() *const* = 0; > *virtual* PxBroadcastingAllocator& getAllocator() *const* = 0; > *virtual* PxAllocatorCallback& getAllocatorCallback() *const* = 0; > *virtual* *bool* getReportAllocationNames() *const* = 0; > *virtual* *void* setReportAllocationNames(*bool* value) = 0; > > *virtual* ~PxFoundation() {} > }; > > > > - The wrapping of PxFoundation makes no problem. > > > > > > To make sure that I made no mistake with the initialization of PhysX, > I tried a different solution. > > A small function InitPhysX create the foundation, and GetFoundation > get this. > > > > C++ Code: > > > *using* *namespace* physx; > > PxU32 PHYSICS_VERSION = PX_PHYSICS_VERSION; > *static* PxFoundation *mFoundation = NULL; > *static* PxDefaultErrorCallback gDefaultErrorCallback; > *static* PxDefaultAllocator gDefaultAllocatorCallback; > > > PxFoundation* GetFoundation(){ > *return* mFoundation; > } > > *void* InitPhysX() { > mFoundation = PxCreateFoundation( > PX_PHYSICS_VERSION, > gDefaultAllocatorCallback, > gDefaultErrorCallback); > > *if*(!mFoundation) > printf("ERROR: PxCreateFoundation failed!\n"); > > > *else* printf("PxCreateFoundation created!\n"); > } > > > > The wrapped python program: > > > > 1 import _physx324_d as PX > > 2 PX.InitPhysX() > > 3 foundation = PX.GetFoundation() > > > > I get on line 2 the message: "PxCreateFoundation created!" > => OK! > > > > On Line 3 the same error RuntimeError: Access violation - no RTTI data! > > > > Now i check the wrappings of PxCreateFoundation in > _physx324_d_free_functions.pypp.cpp > > > > void register_free_functions(){ > > . . . > > > > { //::GetFoundation > > typedef ::physx::PxFoundation * ( *GetFoundation_function_type > )( ); > > bp::def( > "GetFoundation" > , GetFoundation_function_type( &::GetFoundation ) > , bp::return_value_policy< bp::reference_existing_object > >() ); > > } > > > > . . . > > > > > > I think: return_value_policy< bp::reference_existing_object > thats > right!? > > > > Then a debug session with PTVS, start with a break point in InitPhysX > > and inspect the mFoundation after the successful generation. > > Its a vptr with 9 Entries => thats right, PxFoundation has 9 Methods. > > That's all what I can see, because I have no source code and no pdb > (symbols). > > > > I place the next Breakpoint in > > PxFoundation* GetFoundation(){ > *return* mFoundation; > } > > > > to search the Error location. > > > > Then followed a trace trip through the code, for me is a journey > through an unreadable jungles of wrapper C + + code. > > Unfortunately, I am not an C++Expert. > > The Error is not to find for me. > > > > > > The same problem occurs with PxCreatePhysics. > > > > My work enviroment: > > ? Windows 7 x64 > > ? Python 2.7 > > ? physxVersion 3.24 (i try: 3.01, 3.23, 3.3, same problem) > > ? visualStudioVersion 11 (i try: VS 9 and VS 10, same problem) > > ? PythonTools for Visual Studio (PTVS) > > ? Boost 1.55 (i try: 1.45, same problem) > > ? gccxml 0.9 > > ? pyplusplus 1.0 svn 1.5.1 > > ? pygccxml 1.0 svn 1.5.1 > > > > > > > > What is my mistake? > > I would be very grateful if someone could an expert help. > > Thanks for your response. > > > > Peter Armold > > > > > > > > > > > > > > > > _______________________________________________ > Cplusplus-sig mailing list > Cplusplus-sig(a)python.org > https://mail.python.org/mailman/listinfo/cplusplus-sig >

1 0

PhysX3.x Wrapping Problems
by Peter Armbrüster Jan. 29, 2014

Jan. 29, 2014

Dear Boost.python, C++ and Py++ Experts, this is my first post in your excellent Forum. I have chosen as the wrapper software the boost.python/Py++ Package to write a physx 3.x Wrapper, because I think it is the best. Many many thanks to David Abrahams and Roman Yakovenko for the great Tools. The wrapping of old versions physx 2.x had made no problems. And now I come across a very big problem at the 3.x Versions. All wrappings of classes works very well. The problem only exists in the PhysX free functions, which are responsible for the initialization of PhysX. I try to explain with a reduced Example. The initialization of PhysX starts with create of foundation : 0 static PxFoundation *mFoundation = NULL; 1 static PxDefaultErrorCallback gDefaultErrorCallback; 2 static PxDefaultAllocator gDefaultAllocatorCallback; 3 mFoundation = PxCreateFoundation(PX_PHYSICS_VERSION, gDefaultAllocatorCallback, gDefaultErrorCallback); 4 4 if(!mFoundation) 5 fatalError("PxCreateFoundation failed!"); The wrapped python program generate a runtime error at line 3: RuntimeError: Access violation - no RTTI data! Its impossible to get mFoundation. Notes: - physx comes as SDK: only Headers, libs and dlls. - PxFoundation is a Abstract class: class PX_FOUNDATION_API PxFoundation { public: virtual void release() = 0; virtual PxErrorCallback& getErrorCallback() const = 0; virtual void setErrorLevel(PxErrorCode::Enum mask = PxErrorCode::eMASK_ALL) = 0; virtual PxErrorCode::Enum getErrorLevel() const = 0; virtual PxBroadcastingAllocator& getAllocator() const = 0; virtual PxAllocatorCallback& getAllocatorCallback() const = 0; virtual bool getReportAllocationNames() const = 0; virtual void setReportAllocationNames(bool value) = 0; virtual ~PxFoundation() {} }; - The wrapping of PxFoundation makes no problem. To make sure that I made no mistake with the initialization of PhysX, I tried a different solution. A small function InitPhysX create the foundation, and GetFoundation get this. C++ Code: using namespace physx; PxU32 PHYSICS_VERSION = PX_PHYSICS_VERSION; static PxFoundation *mFoundation = NULL; static PxDefaultErrorCallback gDefaultErrorCallback; static PxDefaultAllocator gDefaultAllocatorCallback; PxFoundation* GetFoundation(){ return mFoundation; } void InitPhysX() { mFoundation = PxCreateFoundation( PX_PHYSICS_VERSION, gDefaultAllocatorCallback, gDefaultErrorCallback); if(!mFoundation) printf("ERROR: PxCreateFoundation failed!\n"); else printf("PxCreateFoundation created!\n"); } The wrapped python program: 1 import _physx324_d as PX 2 PX.InitPhysX() 3 foundation = PX.GetFoundation() I get on line 2 the message: "PxCreateFoundation created!" => OK! On Line 3 the same error RuntimeError: Access violation - no RTTI data! Now i check the wrappings of PxCreateFoundation in _physx324_d_free_functions.pypp.cpp void register_free_functions(){ . . . { //::GetFoundation typedef ::physx::PxFoundation * ( *GetFoundation_function_type )( ); bp::def( "GetFoundation" , GetFoundation_function_type( &::GetFoundation ) , bp::return_value_policy< bp::reference_existing_object >() ); } . . . I think: return_value_policy< bp::reference_existing_object > thats right!? Then a debug session with PTVS, start with a break point in InitPhysX and inspect the mFoundation after the successful generation. Its a vptr with 9 Entries => thats right, PxFoundation has 9 Methods. That's all what I can see, because I have no source code and no pdb (symbols). I place the next Breakpoint in PxFoundation* GetFoundation(){ return mFoundation; } to search the Error location. Then followed a trace trip through the code, for me is a journey through an unreadable jungles of wrapper C + + code. Unfortunately, I am not an C++Expert. The Error is not to find for me. The same problem occurs with PxCreatePhysics. My work enviroment: · Windows 7 x64 · Python 2.7 · physxVersion 3.24 (i try: 3.01, 3.23, 3.3, same problem) · visualStudioVersion 11 (i try: VS 9 and VS 10, same problem) · PythonTools for Visual Studio (PTVS) · Boost 1.55 (i try: 1.45, same problem) · gccxml 0.9 · pyplusplus 1.0 svn 1.5.1 · pygccxml 1.0 svn 1.5.1 What is my mistake? I would be very grateful if someone could an expert help. Thanks for your response. Peter Armold

4 3

Re: [C++-sig] Cplusplus-sig Digest, Vol 64, Issue 11
by Peter Armbrüster Jan. 29, 2014

Jan. 29, 2014

Hi Niki and Giuseppe, thanks for your answers, but once I had already considered . My compiler flags are: /DWIN32 /DDEBUG /GR /RTCsu /DPX_DEBUG I wish you a nice day. Peter -----Ursprüngliche Nachricht----- Von: Cplusplus-sig [mailto:cplusplus-sig-bounces+arm=rfh-koeln.de@python.org] Im Auftrag von cplusplus-sig-request(a)python.org Gesendet: Mittwoch, 29. Januar 2014 12:00 An: cplusplus-sig(a)python.org Betreff: Cplusplus-sig Digest, Vol 64, Issue 11 Send Cplusplus-sig mailing list submissions to cplusplus-sig(a)python.org To subscribe or unsubscribe via the World Wide Web, visit https://mail.python.org/mailman/listinfo/cplusplus-sig or, via email, send a message with subject or body 'help' to cplusplus-sig-request(a)python.org You can reach the person managing the list at cplusplus-sig-owner(a)python.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Cplusplus-sig digest..." Today's Topics: 1. Re: PhysX3.x Wrapping Problems (niki) 2. Re: PhysX3.x Wrapping Problems (Giuseppe Corbelli) ---------------------------------------------------------------------- Message: 1 Date: Wed, 29 Jan 2014 10:19:59 +0200 From: niki <niki(a)vintech.bg> To: Development of Python/C++ integration <cplusplus-sig(a)python.org> Subject: Re: [C++-sig] PhysX3.x Wrapping Problems Message-ID: <52E8B9AF.4050602(a)vintech.bg> Content-Type: text/plain; charset=UTF-8; format=flowed On 28.01.2014 18:33, Peter Armbr?ster wrote: > Dear Boost.python, C++ and Py++ Experts, > > this is my first post in your excellent Forum. > > I have chosen as the wrapper software the boost.python/Py++ Packageto > write a physx 3.x Wrapper, because I think it is the best. > > Many many thanks to David Abrahams and Roman Yakovenko for the great Tools. > > The wrapping of old versions physx 2.x had made no problems. > > And now I come across a very big problem at the 3.x Versions. > > All wrappings of classes works very well. > > The problem only exists in the PhysX free functions, which are > responsible for the initialization of PhysX. > > I try to explain with a reduced Example. > > The initialization of PhysX starts with create of foundation : > > *0 static*PxFoundation*mFoundation=NULL; > > *1 static*PxDefaultErrorCallbackgDefaultErrorCallback; > *2 static*PxDefaultAllocatorgDefaultAllocatorCallback; > 3 > mFoundation=PxCreateFoundation(PX_PHYSICS_VERSION,gDefaultAllocatorCal > lback,gDefaultErrorCallback);4 > *4 if*(!mFoundation) > > 5 fatalError("PxCreateFoundation failed!"); > > The wrapped python program generate a runtime error at line > 3:RuntimeError: Access violation - no RTTI data! Just wild guess: add compiler option to enable RTTI HTH Niki ------------------------------ Message: 2 Date: Wed, 29 Jan 2014 11:03:00 +0100 From: Giuseppe Corbelli <giuseppe.corbelli(a)copanitalia.com> To: Development of Python/C++ integration <cplusplus-sig(a)python.org> Subject: Re: [C++-sig] PhysX3.x Wrapping Problems Message-ID: <52E8D1D4.7060003(a)copanitalia.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 28/01/2014 17:33, Peter Armbr?ster wrote: > Dear Boost.python, C++ and Py++ Experts, > > this is my first post in your excellent Forum. > > I have chosen as the wrapper software the boost.python/Py++ Packageto > write a physx 3.x Wrapper, because I think it is the best. > > Many many thanks to David Abrahams and Roman Yakovenko for the great Tools. > > The wrapping of old versions physx 2.x had made no problems. > > And now I come across a very big problem at the 3.x Versions. > > All wrappings of classes works very well. > > The problem only exists in the PhysX free functions, which are > responsible for the initialization of PhysX. > > I try to explain with a reduced Example. > > The initialization of PhysX starts with create of foundation : > > *0 static*PxFoundation*mFoundation=NULL; > > *1 static*PxDefaultErrorCallbackgDefaultErrorCallback; > *2 static*PxDefaultAllocatorgDefaultAllocatorCallback; > 3 > mFoundation=PxCreateFoundation(PX_PHYSICS_VERSION,gDefaultAllocatorCal > lback,gDefaultErrorCallback);4 > *4 if*(!mFoundation) > > 5 fatalError("PxCreateFoundation failed!"); > > The wrapped python program generate a runtime error at line 3:RuntimeError: > Access violation - no RTTI data! > > Its impossible to get mFoundation. > > *Notes: * > > - physx comes as SDK: only Headers, libs and dlls. Before reading on I'd investigate the "no RTTI data" message. Make sure you're using the /GR compiler option. -- Giuseppe Corbelli WASP Software Engineer, Copan Italia S.p.A Phone: +390303666318 Fax: +390302659932 E-mail: giuseppe.corbelli(a)copanitalia.com ------------------------------ Subject: Digest Footer _______________________________________________ Cplusplus-sig mailing list Cplusplus-sig(a)python.org https://mail.python.org/mailman/listinfo/cplusplus-sig ------------------------------ End of Cplusplus-sig Digest, Vol 64, Issue 11 *********************************************

1 0

create a python object from scratch in boost.python?
by Gary Oberbrunner Jan. 21, 2014

Jan. 21, 2014

I'd like to create a python object with some attributes in C++, and return it to python. Something like this: Plugin_Info *pinfo = get_plugin_info_i(i); bp::object plugin; // this creates None; how can I make an empty class? plugin.attr("name") = std::string(pinfo->plugin_name); plugin.attr("category") = std::string(pinfo->category); plugin.attr("n_effects") = (int)pinfo->n_effects; plugin.attr("n_inputs") = (int)pinfo->n_inputs; plugin.attr("custom_p") = (int)pinfo->custom_p; effect_list.append(plugin); But this fails on the third line, because the "plugin" object is None, and None has no attributes. Instead of None, I'd like to create a simple empty python class I can add attributes to. How can I do that? (Yes, I could use a dict instead but the python side would like to see attributes with values rather than a dict.) -- . . . . . . . . . . . . . . . . . . . . . . Gary Oberbrunner garyo(a)genarts.com VP Engineering Tel: 617-492-2888 GenArts, Inc. www.genarts.com

4 11

Using Numpy C API with boost python numeric
by Александров Петр Jan. 17, 2014

Jan. 17, 2014

Is it safe to use direct Numpy C API in Boost Python module together with Boost Python numeric::array (also using numpy)? The function "import_array" must be called before using PyArray_SimpeNew. Will it cause problems if the function "import_array" will be called twice in one module?

2 1

How to handle argument error exceptions in boost.python?
by Gary Oberbrunner Jan. 14, 2014

Jan. 14, 2014

[I posted this on StackOverflow yesterday, but got nothing. Hoping you will have some insight!] I'm writing a C++ python extension. I have a boost::python extension function static void EXTrender_effect(EffectGlobals_t *effect_handle, std::string preset, bp::object dest, int xdim, int ydim) { ... } that I export as usual in my boost.python extension: def("render_effect", EXTrender_effect); When I call that from python(2.7), I get a C++ exception boost::python::error_already_set. Tracing that down in Visual Studio, I can see it's coming from a boost::python::objects::function::argument_error. So OK, I have an argument error; I'm probably calling it with the wrong args. What I'd like to do is print or throw something sensible in my python extension when this happens, so users of my extension will see the nice message that I know is lurking in PyErr_Fetch. (I can see the message getting built in the boost.python argument_error code.) But I can't catch that error_already_set; boost.python does that internally around the funcall. And I can't check for python errors in my extension code, since my function never gets called (the argument error is detected by boost.python). What ends up happening is it just silently fails. What can I hook up so I (or my users) can see the argument error messages? And ideally convert those into python exceptions? This is all Win7, Python2.7. -- . . . . . . . . . . . . . . . . . . . . . . Gary Oberbrunner garyo(a)genarts.com VP Engineering Tel: 617-492-2888 GenArts, Inc. www.genarts.com

4 7

BoostPython: C++ function with "non-const double reference" argument issue. Python looks for float causing argument mismatch.
by Liam Herron Jan. 14, 2014

Jan. 14, 2014

Here is my example: ------------------------------------------------------------------------------------------- CPP Code: ------------------------------------------------------------------------------------------- #include <boost/python.hpp> using namespace boost::python; void updateDoubleReference(double& x) { x = x + 5.4321; } BOOST_PYTHON_MODULE(_testDR) { // Add regular functions to the module. def("updateDoubleReference", &updateDoubleReference ); } ------------------------------------------------------------------------------------------- ------------------------------------------------------------------------------------------- PY Code: ------------------------------------------------------------------------------------------- #!/usr/bin/python # # from _testDR import * x = 3.0 updateDoubleReference(x) -------------------------------------------------------------------------------------------- ------------------------------------------------------------------------------------------- ERROR OUTPUT ------------------------------------------------------------------------------------------- python2.5 testDR.py Traceback (most recent call last): File "testDR.py", line 8, in <module> updateDoubleReference(x) Boost.Python.ArgumentError: Python argument types in _testDR.updateDoubleReference(float) did not match C++ signature: updateDoubleReference(double {lvalue}) ------------------------------------------------------------------------------------------- How do people typically handle this issue? Wrap the function with 'float' versions of the arguments? I tried to create a 'NativeDouble' struct that had a double member attribute but when exposed to python, it simply interprets this as a float and it still has a mismatch. Any help would be greatly appreciated. Thanks, Liam ============================================================================================= Email transmissions can not be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of email transmission. In addition, the information contained in this email message is intended only for use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution,or copying of this communication, disclosure of the parties to it, or any action taken or omitted to be taken in reliance on it, is strictly prohibited, and may be unlawful. If you are not the intended recipient please delete this email message. ==============================================================================================

2 1

Re: [C++-sig] How to handle argument error exceptions in boost.python?
by Charly Bicker Jan. 10, 2014

Jan. 10, 2014

1 0