Mailman 3 October 2005 - Cplusplus-sig

Expression templates in python
by David Welch Oct. 11, 2005

Oct. 11, 2005

Hi, I am new to python and thought I would write a vector / matrix class in c++ and export to python. Is it possible to have vector operations done in python evaluate to some form of intermediate calculation object which can then be passed to the c++ code for evaluation? ie, V1 = [0.1,0.2,0.3] V2 = [0.7,0.4,0.7] V3 = V1*4 - V2*V1 so the operators in python would not actually do the calulation but construct an object which will call a c++ function on assignment to V3 ala expression templates in c++. Has this been done before in python, if so is there a link? Also, is it possible to pass a lambda function as an argument to a c function and get information about its contents? Any advice on how to do this, is it worth it? Thanks, Dave

3 3

Re: [C++-sig] Memory Leaks In VS.NET 2003 With BOOST_PYTHON_MODULE
by Matthew B. Keyes Oct. 10, 2005

Oct. 10, 2005

Ralf, Thanks tons again for the help! Needless to say, that will save me from pulling my hair out over this :) Thanks again, Matt "Ralf W. Grosse-Kunstleve" <rwgk(a)yahoo.com> wrote in message news:<20051010190642.45158.qmail(a)web31502.mail.mud.yahoo.com>... > --- mjkeyes(a)sbcglobal.net wrote: > > > Ralf (et. al), > > > > (note - I hope my newsgroup reader doesn't wrap all this in one line) > > > > I've been playing around with this and I'm still thinking boost leaks > > memory in an embedded and extended application. I use Visual Leak > > Detector 1.0 to track memory leaks, and here is where the leak comes > > from (in my code): > > ... > > If I insert VLDDisable() before this class_ block and VLDEnable() after > > (which temporarily disables the leak detection for this function call), > > I get zero leaks. With it turned on, here is what I see (repeated 17 > > times): > > ... > > d:\devl\muds\testbed\completelibtest\thirdlibtest\lib\pythoninputhandler > > .h (153): init_module_PyInputHandler > > 0x10006C2B (File and line number not available): > > boost::python::detail::exception_handler::operator= > > 0x1000EC23 (File and line number not available): > > boost::python::detail::init_module > > 0x1E0682B1 (File and line number not available): PyImport_FindModule > > 0x48747570 (File and line number not available): (Function name > > unavailable) > > Data: > > ... (whatever data leaked) > > I believe these leaks are not actually leaks, but a documented > (http://www.boost.org/libs/python/todo.html) feature of Boost.Python, directly > connected to the lack of support for PyFinalize(). I think what you are seeing > as leaks are actually just entries in the global converter registry. These are > one-time static allocations. Since you cannot dlopen the same module multiple > times there is no danger that these allocations become a real problem. > See also: boost/libs/python/src/converter/registry.cpp > > Why is PyFinalize() support missing? -- Simply because the groups who invested > money into Boost.Python development had no interest in embedding. > > To find real leaks, please consider my very simple approach of calling the code > with the suspected problem in an infinite loop while monitoring the memory > allocation of the process. Simple, quick, very effective, works the same on all > platforms. I've done it many times, coincidentally a couple of days ago while > testing new low-level code. I didn't see any real leaks. > > Cheers, > Ralf > > > > > __________________________________ > Yahoo! Music Unlimited > Access over 1 million songs. Try it free. > http://music.yahoo.com/unlimited/

1 0

Re: [C++-sig] Memory Leaks In VS.NET 2003 With BOOST_PYTHON_MODULE
by mjkeyes＠sbcglobal.net Oct. 10, 2005

Oct. 10, 2005

Ralf (et. al), (note - I hope my newsgroup reader doesn't wrap all this in one line) I've been playing around with this and I'm still thinking boost leaks memory in an embedded and extended application. I use Visual Leak Detector 1.0 to track memory leaks, and here is where the leak comes from (in my code): BOOST_PYTHON_MODULE(PyInputHandler) { class_<Extensions::PythonInputHandler,boost::noncopyable>("PythonInputHa ndler") .def("HandleInput", pure_virtual(&SocketLib::InputHandler<std::string>::HandleInput)) .def("Enter", pure_virtual(&SocketLib::InputHandler<std::string>::Enter)) .def("Leave", pure_virtual(&SocketLib::InputHandler<std::string>::Leave)) .def("Hungup", pure_virtual(&SocketLib::InputHandler<std::string>::Hungup)) .def("Flooded", pure_virtual(&SocketLib::InputHandler<std::string>::Flooded)) .def("NoRoom", pure_virtual(&SocketLib::InputHandler<std::string>::NoRoom)) .def("Quit", &Extensions::PythonInputHandler::Quit) .def("ShutDown", &Extensions::PythonInputHandler::ShutDown) .def("SendGlobal", &Extensions::PythonInputHandler::SendGlobal) .def("AddInputHandler", &Extensions::PythonInputHandler::AddInputHandler) ; } If I insert VLDDisable() before this class_ block and VLDEnable() after (which temporarily disables the leak detection for this function call), I get zero leaks. With it turned on, here is what I see (repeated 17 times): (note - the block varies for each leak) ---------- Block 166 at 0x003A7520: 8 bytes ---------- Call Stack: f:\vs70builds\3077\vc\crtbld\crt\src\newop.cpp (12): operator new d:\devltool\boost\boost_1_33_0\boost\python\object\py_function.hpp (121): boost::python::objects::py_function::py_function<boost::python::detail:: caller<void (__cdecl*)(_object *),boost::python::default_call_policies,boost::mpl::vector2<void,_object *> > > d:\devltool\boost\boost_1_33_0\boost\python\make_function.hpp (62): boost::python::detail::make_function_aux<void (__cdecl*)(_object *),boost::python::default_call_policies,boost::mpl::vector2<void,_object *>,boost::mpl::int_<0> > d:\devltool\boost\boost_1_33_0\boost\python\detail\make_keyword_range_fn .hpp (32): boost::python::detail::make_keyword_range_function<void (__cdecl*)(_object *),boost::python::default_call_policies> d:\devltool\boost\boost_1_33_0\boost\python\detail\make_keyword_range_fn .hpp (64): boost::python::detail::make_keyword_range_constructor<boost::mpl::vector 0<boost::mpl::na>,boost::mpl::size<boost::mpl::vector0<boost::mpl::na> >,boost::python::objects::value_holder<Extensions::PythonInputHandler>,b oost::python::default_call_policies> d:\devltool\boost\boost_1_33_0\boost\python\init.hpp (338): boost::python::detail::make_keyword_range_constructor<boost::mpl::vector 0<boost::mpl::na>,boost::mpl::size<boost::mpl::vector0<boost::mpl::na> >,boost::python::objects::value_holder<Extensions::PythonInputHandler>,b oost::python::default_call_policies> d:\devltool\boost\boost_1_33_0\boost\python\init.hpp (399): boost::python::detail::make_keyword_range_constructor<boost::mpl::vector 0<boost::mpl::na>,boost::mpl::size<boost::mpl::vector0<boost::mpl::na> >,boost::python::objects::value_holder<Extensions::PythonInputHandler>,b oost::python::default_call_policies> d:\devltool\boost\boost_1_33_0\boost\python\init.hpp (177): boost::python::detail::make_keyword_range_constructor<boost::mpl::vector 0<boost::mpl::na>,boost::mpl::size<boost::mpl::vector0<boost::mpl::na> >,boost::python::objects::value_holder<Extensions::PythonInputHandler>,b oost::python::default_call_policies> d:\devltool\boost\boost_1_33_0\boost\python\def_visitor.hpp (32): boost::python::detail::make_keyword_range_constructor<boost::mpl::vector 0<boost::mpl::na>,boost::mpl::size<boost::mpl::vector0<boost::mpl::na> >,boost::python::objects::value_holder<Extensions::PythonInputHandler>,b oost::python::default_call_policies> d:\devltool\boost\boost_1_33_0\boost\python\def_visitor.hpp (67): boost::python::detail::make_keyword_range_constructor<boost::mpl::vector 0<boost::mpl::na>,boost::mpl::size<boost::mpl::vector0<boost::mpl::na> >,boost::python::objects::value_holder<Extensions::PythonInputHandler>,b oost::python::default_call_policies> d:\devltool\boost\boost_1_33_0\boost\python\class.hpp (226): boost::python::detail::make_keyword_range_constructor<boost::mpl::vector 0<boost::mpl::na>,boost::mpl::size<boost::mpl::vector0<boost::mpl::na> >,boost::python::objects::value_holder<Extensions::PythonInputHandler>,b oost::python::default_call_policies> d:\devltool\boost\boost_1_33_0\boost\python\class.hpp (502): boost::python::detail::make_keyword_range_constructor<boost::mpl::vector 0<boost::mpl::na>,boost::mpl::size<boost::mpl::vector0<boost::mpl::na> >,boost::python::objects::value_holder<Extensions::PythonInputHandler>,b oost::python::default_call_policies> d:\devltool\boost\boost_1_33_0\boost\python\class.hpp (631): boost::python::detail::make_keyword_range_constructor<boost::mpl::vector 0<boost::mpl::na>,boost::mpl::size<boost::mpl::vector0<boost::mpl::na> >,boost::python::objects::value_holder<Extensions::PythonInputHandler>,b oost::python::default_call_policies> d:\devl\muds\testbed\completelibtest\thirdlibtest\lib\pythoninputhandler .h (153): init_module_PyInputHandler 0x10006C2B (File and line number not available): boost::python::detail::exception_handler::operator= 0x1000EC23 (File and line number not available): boost::python::detail::init_module 0x1E0682B1 (File and line number not available): PyImport_FindModule 0x48747570 (File and line number not available): (Function name unavailable) Data: ... (whatever data leaked) It appears in py_function.hpp, the following line is the culprit: struct py_function { template <class Caller> py_function(Caller const& caller) (line 120 - leak): : m_impl(new caller_py_function_impl<Caller>(caller)) {} /*...*/ }; This m_impl is a std::auto_ptr<py_function_impl_base>, and the constructor is given a new caller_py_function_impl. However, I don't know that this is ever deallocated. I could be terribly wrong here, but if I run my code without this BOOST_INIT_MODULE call, I get no leaks. Is this something that Python will deallocate? Any advice is appreciated! Thanks! Matt "Ralf W. Grosse-Kunstleve" <rwgk(a)yahoo.com> wrote in message news:<20051007232909.9702.qmail(a)web31514.mail.mud.yahoo.com>... > --- Matt <mjkeyes(a)sbcglobal.net> wrote: > > handle<> hInitPtr(PyImport_ImportModule( "Python.SnakeMUD" )); > > I think this is correct code, and I know for sure the handle<> > constructor doesn't introduce memory leaks. But I don't know what > "Python.SnakeMUD" is. What happens if you import "sys" instead? > > > However, when I uncomment even just the first line (the hInitPtr), I > > get 17 leaks. > > How do you measure memory leaks? > E.g. dynamically loading modules is irreversible in C Python. I could > imagine some associated allocation overhead that is not de-allocated > until the process finishes. If I suspect a leak somewhere my usual > response is to call the corresponding functions repeatedly in an > infinite loop and manually monitor the total allocation of the process > (e.g. "top" under Linux or the Task Manager under Windows). With this > method even tiny leaks usually show up very quickly on the radar, > while one-time static allocations connected to imports or other static > initializers don't create any visible noise. > > Cheers, > Ralf > > > > > __________________________________ > Yahoo! Mail - PC Magazine Editors' Choice 2005 > http://mail.yahoo.com

2 1

Re: [C++-sig] Help With Embedded Pure Virtual Classes
by mjkeyes＠sbcglobal.net Oct. 10, 2005

Oct. 10, 2005

Easy fix: BOOST_PYTHON_MODULE(PyInputHandler) { class_<InputHandler<std::string>,PythonLib::PythonInputHandler,boost::no ncopyable>("PythonInputHandler") .def("HandleInput", pure_virtual(&InputHandler<std::string>::HandleInput)) /*...other exposed pure methods...*/ ; } Should be: BOOST_PYTHON_MODULE(PyInputHandler) { class_<PythonLib::PythonInputHandler,boost::noncopyable>("PythonInputHan dler") .def("HandleInput", pure_virtual(&InputHandler<std::string>::HandleInput)) /*...other exposed pure methods...*/ ; } "Matt" <mjkeyes(a)sbcglobal.net> wrote in message news:<di8u7g$2fu$1(a)sea.gmane.org>... > Hey all, > > (there is quite some code below... my apologies in advance, but there > should > be a fairly simple solution to this question I'm sure) > > My apologies for spamming the mailing list lately... i'm just trying > to get > off to a good start working with embedding Python in C//C++. (Thanks to > Ralf thus far for his help, too!) > > Anyways, here's my current problem. i am finally able to get an > instance of > a class derived in Python from a pure virtual class in C++ created. > However, i am not able to call any of the pure virtual methods. One of the > base classes from the intermediate "wrapper" class is the > boost::python::wrapper class, but it's own internal object never gets set > (and i don't think there is a way to manually set it since it is a private > variable). > > Here is some of my code: > > /***********************************************************/ > //Base pure class: > template<class commandtype> > class InputHandler > { > //Pure Functions > public: > virtual commandtype HandleInput(const commandtype &Input) = 0; > virtual commandtype Enter() = 0; virtual commandtype Leave() = 0; > virtual commandtype Hungup() = 0; > virtual commandtype Flooded() = 0; > virtual commandtype NoRoom() = 0; > //End Pure Functions > /*...*/ > }; > > //Intermediate class: > class PythonInputHandler : public InputHandler<std::string>, public > wrapper<InputHandler<std::string> > > { > public: > PythonInputHandler(PyObject *pSelf = NULL) : m_Self(pSelf) {} > PythonInputHandler(PyObject *pSelf, const InputHandler<std::string> &rhs) : > InputHandler<std::string>(rhs) , m_Self(pSelf) {} > virtual ~PythonInputHandler() {} > > std::string HandleInput(const std::string &Input) > { > const char *p = ""; //note, std::string always causes heap error, so > use > char > try > { > #if BOOST_WORKAROUND(BOOST_MSVC, <= 1300) // Workaround for vc6/vc7 > p = call<char*>(this->get_override("HandleInput").ptr(), Input.c_str()); > #else > p = this->get_override("HandleInput")(Input); > #endif > } > catch(...) > { > PyErr_Print(); > p = ""; > } > > return (p != NULL ? p : ""); > } > /*..other overriden pure methods...*/ > }; > > //NOTE, SORRY AT THIS POINT I HAVE TO DOUBLESPACE EVERYTHING //BECAUSE > MY NEWSGROUP READER WANTS TO WRAP EVERYTHING IN ONE LINE > > BOOST_PYTHON_MODULE(PyInputHandler) > > { > > class_<InputHandler<std::string>,PythonLib::PythonInputHandler,boost:: > noncopyable>("PythonInputHandler") > > .def("HandleInput", > pure_virtual(&InputHandler<std::string>::HandleInput)) > > /*...other exposed pure methods...*/ > > ; > > } > > > //Python code: > > from PyInputHandler import * > > > > class PyLogonHandler(PythonInputHandler): > > def HandleInput(self,Input): > > if Input == "/quit": > > self.Quit() > > elif Input == "/shutdown": > > self.ShutDown() > > else: > > return Input > > #other expose methods... > > > > //Code to instantiate the object in C++: > > try > > { > > handle<> hModulePtr(PyImport_ImportModule( "MyModule" )); > > handle<> hNamespace(borrowed(PyModule_GetDict(hModulePtr.get()))); > > > > handle<> hClassPtr(PyRun_String("PyLogonHandler", Py_eval_input, > hNamespace.get(), hNamespace.get())); > > object oClass(hClassPtr); > > PyErr_Print(); > > > > object oHandler = oClass(); > > PythonLib::PythonInputHandler *pHandler = > extract<PythonLib::PythonInputHandler*>(oHandler); > > > > m_Obj.push(oHandler); //so the object doesn't destruct itself after > this is > finished (making the pointer invalid) > > AddInputHandler(pHandler); > > pHandler->HandleInput("testing"); > > } > > catch(...) > > { > > PyErr_Print(); > > } > > > > /***********************************************************/ > > Now then, everything works great. However, when I call the pure > functions > from C++, the following occurs: > > //code from above in PythonInputHandler > std::string HandleInput(const std::string &Input) > { > const char *p = ""; //note, std::string always causes heap error, so > use > char > try > { > #if BOOST_WORKAROUND(BOOST_MSVC, <= 1300) // Workaround for vc6/vc7 > p = call<char*>(this->get_override("HandleInput").ptr(), Input.c_str()); > #else > p = this->get_override("HandleInput")(Input); //THROWS EXCEPTION BECAUSE > INTERNAL OBJECT IS NULL > #endif > } > catch(...) > { > PyErr_Print(); > p = ""; > } > > I can't seem to get the internal wrapper's internal object > (representing the > acutal Python class) set. I'm sure I'm missing something simple, but I'm > having difficulty tracking it down (and I can't find any tutorials that tie > all this together in a way that will allow me to do what I'm trying to do). > > Thanks in advance!! > Matt

1 0

Help With Embedded Pure Virtual Classes
by Matt Oct. 8, 2005

Oct. 8, 2005

Hey all, (there is quite some code below... my apologies in advance, but there should be a fairly simple solution to this question I'm sure) My apologies for spamming the mailing list lately... i'm just trying to get off to a good start working with embedding Python in C//C++. (Thanks to Ralf thus far for his help, too!) Anyways, here's my current problem. i am finally able to get an instance of a class derived in Python from a pure virtual class in C++ created. However, i am not able to call any of the pure virtual methods. One of the base classes from the intermediate "wrapper" class is the boost::python::wrapper class, but it's own internal object never gets set (and i don't think there is a way to manually set it since it is a private variable). Here is some of my code: /***********************************************************/ //Base pure class: template<class commandtype> class InputHandler { //Pure Functions public: virtual commandtype HandleInput(const commandtype &Input) = 0; virtual commandtype Enter() = 0; virtual commandtype Leave() = 0; virtual commandtype Hungup() = 0; virtual commandtype Flooded() = 0; virtual commandtype NoRoom() = 0; //End Pure Functions /*...*/ }; //Intermediate class: class PythonInputHandler : public InputHandler<std::string>, public wrapper<InputHandler<std::string> > { public: PythonInputHandler(PyObject *pSelf = NULL) : m_Self(pSelf) {} PythonInputHandler(PyObject *pSelf, const InputHandler<std::string> &rhs) : InputHandler<std::string>(rhs) , m_Self(pSelf) {} virtual ~PythonInputHandler() {} std::string HandleInput(const std::string &Input) { const char *p = ""; //note, std::string always causes heap error, so use char try { #if BOOST_WORKAROUND(BOOST_MSVC, <= 1300) // Workaround for vc6/vc7 p = call<char*>(this->get_override("HandleInput").ptr(), Input.c_str()); #else p = this->get_override("HandleInput")(Input); #endif } catch(...) { PyErr_Print(); p = ""; } return (p != NULL ? p : ""); } /*..other overriden pure methods...*/ }; //NOTE, SORRY AT THIS POINT I HAVE TO DOUBLESPACE EVERYTHING //BECAUSE MY NEWSGROUP READER WANTS TO WRAP EVERYTHING IN ONE LINE BOOST_PYTHON_MODULE(PyInputHandler) { class_<InputHandler<std::string>,PythonLib::PythonInputHandler,boost::noncopyable>("PythonInputHandler") .def("HandleInput", pure_virtual(&InputHandler<std::string>::HandleInput)) /*...other exposed pure methods...*/ ; } //Python code: from PyInputHandler import * class PyLogonHandler(PythonInputHandler): def HandleInput(self,Input): if Input == "/quit": self.Quit() elif Input == "/shutdown": self.ShutDown() else: return Input #other expose methods... //Code to instantiate the object in C++: try { handle<> hModulePtr(PyImport_ImportModule( "MyModule" )); handle<> hNamespace(borrowed(PyModule_GetDict(hModulePtr.get()))); handle<> hClassPtr(PyRun_String("PyLogonHandler", Py_eval_input, hNamespace.get(), hNamespace.get())); object oClass(hClassPtr); PyErr_Print(); object oHandler = oClass(); PythonLib::PythonInputHandler *pHandler = extract<PythonLib::PythonInputHandler*>(oHandler); m_Obj.push(oHandler); //so the object doesn't destruct itself after this is finished (making the pointer invalid) AddInputHandler(pHandler); pHandler->HandleInput("testing"); } catch(...) { PyErr_Print(); } /***********************************************************/ Now then, everything works great. However, when I call the pure functions from C++, the following occurs: //code from above in PythonInputHandler std::string HandleInput(const std::string &Input) { const char *p = ""; //note, std::string always causes heap error, so use char try { #if BOOST_WORKAROUND(BOOST_MSVC, <= 1300) // Workaround for vc6/vc7 p = call<char*>(this->get_override("HandleInput").ptr(), Input.c_str()); #else p = this->get_override("HandleInput")(Input); //THROWS EXCEPTION BECAUSE INTERNAL OBJECT IS NULL #endif } catch(...) { PyErr_Print(); p = ""; } I can't seem to get the internal wrapper's internal object (representing the acutal Python class) set. I'm sure I'm missing something simple, but I'm having difficulty tracking it down (and I can't find any tutorials that tie all this together in a way that will allow me to do what I'm trying to do). Thanks in advance!! Matt

1 0

Memory Leaks In VS.NET 2003 With BOOST_PYTHON_MODULE
by Matt Oct. 7, 2005

Oct. 7, 2005

Hey all, i know i just posted about something else yesterday, but i have found a number of memory leaks that crop up when i use BOOST_PYTHON_MODULE. Here's what it looks like: //NOTE SocketLib and PythonLib are two of my namespaces BOOST_PYTHON_MODULE(PyInputHandler) { class_<PythonLib::PythonInputHandler,boost::noncopyable>("PythonInputHandler") .def("HandleInput",pure_virtual(&SocketLib::InputHandler<std::string>::HandleInput)) .def("Enter", pure_virtual(&SocketLib::InputHandler<std::string>::Enter)) .def("Leave", pure_virtual(&SocketLib::InputHandler<std::string>::Leave)) .def("Hungup",pure_virtual(&SocketLib::InputHandler<std::string>::Hungup)) .def("Flooded",pure_virtual(&SocketLib::InputHandler<std::string>::Flooded)) .def("NoRoom",pure_virtual(&SocketLib::InputHandler<std::string>::NoRoom)) .def("Quit", &PythonLib::PythonInputHandler::Quit) .def("ShutDown", &PythonLib::PythonInputHandler::ShutDown) .def("SendGlobal", &PythonLib::PythonInputHandler::SendGlobal) .def("AddInputHandler", &PythonLib::PythonInputHandler::AddInputHandler) ;}The leaks (17 of them) come from the init_module_PyInputHandler call that isgenerated from this macro.Here is what I call to instantiate my Python class in C++: PyObject *pInit = PyImport_ImportModule( "Python.SnakeMUD" ); if( pInit == NULL ) { PyErr_Print(); //throw custom exception handling } //call the python method to create our initial input handler handle<> hClassPtr(PyObject_CallMethod(pInit, "CreateInitialHandler",NULL)); //wrap the handle in a boost class object Handler(hClassPtr); //Get out class out of the boost class PythonLib::PythonInputHandler *pHandler =extract<PythonLib::PythonInputHandler*>(Handler); //this will call Py_XINCREF on the PyObject *, which will allow ourhandler to continue to exist after this function exits pHandler->SetPyObject(Handler.ptr()); //cleanup the module call Py_XDECREF(pInit); //add our new handler AddInputHandler(pHandler);Nothing really fancy unless i'm doing something completely stupid. Anyadvice?Thanks in advance!Matt

2 5

Trying to install a module (Agrepy)
by Reggie Smith Oct. 6, 2005

Oct. 6, 2005

Hello, everyone. I am trying to install a python module called agrepy which is a fuzzy string search tool. However, when the makefile runs I get many errors like this: "undefined reference to '_Pystring.... referencing one of the C files that the makefile uses. I am using GCC 3.4.4 and Cygwin 1.5.18 on Win XP SP2. >From scanning previous threads I feel very sure this is a Cygwin specific problem. Am I having it point to the wrong library or something? The makefile is below: VERSION=1.2 # Edit this to point to the directory tree in which Python is found #PYTHONROOT=/sw PYTHONROOT=/usr/local # Linux CC = gcc # When testing # Uncomment one of these when creating C only version for testing (see also output below) # CFLAGS = -g -Wall -Wshaddow -DDEBUG -DDEBUGDEBUG # for agrepy_test # CFLAGS = -g # for agrepy_test (free standing C application) OPTFLAGS = -O3 # The following flag is relevant to Linux but is not not recognized # by MacOS X posix compiler so comment it out LDFLAGS = -shared # Some compilers (not Mac) insist you add -fpic when compiling to get .so LDFLAGS = -shared #-fPIC # For Mac OSX # You will need to make the final argument refer to where the binary lives LDFLAGS = $(PYTHONROOT)/bin/python2.3 CFLAGS= -DPYTHON $(FPIC) $(OPTFLAGS) INCLUDES = -I$(PYTHONROOT)/include/python2.3 ALLOBJS = sagrepy.o lagrepy.o agrepy.o agrepy_wrap.o TESTOBJS = sagrepy.o lagrepy.o agrepy.o # Uncomment output : agrepy_test when building C only version for testing output : _agrepy.pyd # output : agrepy_test # This is a C-only implementation for testing purposes agrepy_test: $(TESTOBJS) $(CC) $(CFLAGS) -o agrepy_test $(TESTOBJS) \usr\local\lib\python2.3 libpython2.3.dll.a _agrepy.pyd : $(ALLOBJS) $(CC) $(LDFLAGS) $(INCLUDES) $(ALLOBJS) -o $@ agrepy_wrap.o : agrepy_wrap.c $(CC) $(CFLAGS) -c agrepy_wrap.c $(INCLUDES) agrepy_wrap.c : agrepy.i swig -python agrepy.i $(ALLOBJS): agrepy.h clean: rm -f $(ALLOBJS) agrepy_wrap.doc new: rm -f $(ALLOBJS) make tarfile: mkdir agrepy_${VERSION} cp `cat FILES` agrepy_${VERSION} cp FILES agrepy_${VERSION} tar cvf agrepy_${VERSION}.tar agrepy_${VERSION} gzip agrepy_${VERSION}.tar /bin/rm -r agrepy_${VERSION} Thanks for any help. Reggie __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

1 0

small operators bug
by Roman Yakovenko Oct. 6, 2005

Oct. 6, 2005

Hi. I think I found bug in boost.python operators treatment. Consider next code: C++ code: template< typename derived_type, typename value_type > struct number{ value_type value; derived_type operator+( const derived_type& x ){ derived_type tmp; tmp.value = value + x.value; return tmp; } }; struct integral : public number< integral, int >{ integral operator+( int x ){ integral tmp; tmp.value = value + x; return tmp; } }; BOOST_PYTHON_MODULE(dummy){ bp::class_< number<integral,int> >( "number" ) .def( bp::self + bp::other< integral >() ) .def_readwrite( "value", &number<integral,int>::value ); bp::class_< integral, bp::bases< number<integral,int> > >( "integral" ) .def( bp::self + bp::other< int >() ); } Python code: i = dummy.integral() i.value = 25 j = i + i The last python statement raises exception: unsupported operand type(s) for +: 'integral' and 'integral' If I remove this line ".def( bp::self + bp::other< int >() );", then all works as expected. Thanks Roman Yakovenko

2 3

Getting a Python type object for a c++ type in wrapper code...
by Alex Mohr Oct. 4, 2005

Oct. 4, 2005

Hi folks, I'm a relative boost.python newbie but I've been doing a ton with it and I'm having a blast. Thanks for such an awesome package. Here's my first newbie question. Suppose I have two C++ classes that I'm wrapping -- Foo and Bar. In the wrapper for Bar, I want there to be an attribute which holds the type Foo. That is, from python I wan to be able to say: >>> Module.Bar.fooType == Module.Foo True Something like def_readonly("fooType", <var-which-holds-type-for-Foo>) would be ideal. I'd also like to be able to do this for python types, like python's float. Is there a simple way to do this in my Boost.Python code? Thanks, Alex

4 4