Mailman 3 September 2006 - Cplusplus-sig

Re: [C++-sig] Py++ - problem withsplit_moduleandreturn_opaque_pointer-policy
by Ganssauge, Gottfried Sept. 26, 2006

Sept. 26, 2006

> -----Original Message----- > From: Ganssauge, Gottfried > Sent: Monday, September 25, 2006 12:39 PM > To: 'Development of Python/C++ integration' > Subject: RE: [C++-sig] Py++ - problem > withsplit_moduleandreturn_opaque_pointer-policy ... > > Also you don't have to add > > BOOST_PYTHON_OPAQUE_SPECIALIZED_TYPE_ID macro > To be exact: I _must_ not add ... > > > Py++ will generate one. > Indeed. > It works quite nice :-) One grain of salt though: Py++ will happily generate more than one if there are several functions returning the same opaque pointer type. This leads to a compilation error: redefinition of 'boost::python::type_info boost::python::type_id() [with T = <opaque pointee type>] In the following test the generated file test_opaque_free_functions.pypp.cpp will contain two instantiations of BOOST_PYTHON_OPAQUE_SPECIALIZED_TYPE_ID( opaque_ ). test.hpp ---8><---><8--- typedef struct opaque_ *opaque_pointer; opaque_pointer get_opaque(); opaque_pointer get2_opaque(); ---8><---><8--- test.py: ---8><---><8--- import os from pyplusplus import module_builder from pyplusplus.decl_wrappers import \ return_value_policy, \ return_opaque_pointer mb = module_builder.module_builder_t( ["test.hpp"] ) mb.free_function (name = "get_opaque").call_policies = \ return_value_policy (return_opaque_pointer) mb.free_function (name = "get2_opaque").call_policies = \ return_value_policy (return_opaque_pointer) mb.build_code_creator( module_name='test_opaque' ) mb.split_module( '.' ) ---8><---><8--- Cheers, Gottfried > > > > -- > > Roman Yakovenko > > C++ Python language binding > > http://www.language-binding.net/ > > _______________________________________________ > > C++-sig mailing list > > C++-sig(a)python.org > > http://mail.python.org/mailman/listinfo/c++-sig > > >

2 2

to Philip Austin:Re: Stuck on accessing numpy.ndarray in c extension
by Qinfeng(Javen) Shi Sept. 26, 2006

Sept. 26, 2006

Hi Philip Austin, Thanks! I added following lines as you told me to hello.cpp file. It didn't crash but still had error. The interesting thing is that now running it twice would get two different error informations. /************hello.cpp**************/ namespace ar=boost::python::numeric; namespace bp=boost::python; import_array(); ar::array::set_module_and_type("numpy", "ndarray"); ########## error report########## >>> import hello >>> import numpy >>> a = numpy.arange(25).reshape((5,5)); >>> hello.testArray(a) // first time SystemError: new style getargs format but argument is not a tuple >>> hello.testArray(a) // second time args is array type! //it means PyArray_Check(args) successed this time. getting input failed! //PyArg_ParseTuple() failed but not crashed Any idea? -- Qinfeng(Javen) Shi Research School of Information Sciences and Engineering Australian National University Locked Bag 8001 Canberra ACT 2601

1 0

Re: [C++-sig] numpy.ndarray did not match PyArrayObject *
by Qinfeng(Javen) Shi Sept. 26, 2006

Sept. 26, 2006

Hi David, I did what you told me. But it reported that PyArrayObject_Type undeclared though I included "arrayobject.h". Any important trick I missed? -- Qinfeng(Javen) Shi Research School of Information Sciences and Engineering Australian National University Locked Bag 8001 Canberra ACT 2601

2 2

return PyObject* failed.
by Qinfeng(Javen) Shi Sept. 26, 2006

Sept. 26, 2006

Dear all, I write a c extension function to access python list. I can visit the list by PyObject* a, but failed when I tried to return PyObject* to python. Any suggestion will be appreciated. >>> list1 = range(5); >>> rlist = hello.testList(list1) 4 3 2 1 0 size:5 b is list type! # seems right now. >>> rlist # but actually it crashed when display the returned rlist Segmentation fault /**************c extension************/ static PyObject * testList(PyObject* a) { if(!(PyList_Check(a))) { printf("not list type!\n"); return NULL; } int num = PyList_Size(a); PyList_Reverse(a); // modify a. for(int i=0;i<num;i++) { printf("%d ",PyInt_AsLong(PyList_GetItem(a,i))); // print it out } printf("size:%d\n",num); PyObject * b = PyList_New(10); // create a new list b if (b == NULL) return NULL; if(!(PyList_Check(b))) // check b { printf("b is not list type!\n"); return NULL; } else { printf("b is list type!\n"); } /**********************works untill now******************/ return (PyObject *)b; /***********failed**/ // return b. in fact,if return a, it also crashed } // Boost Includes ============================================================== #include <boost/python.hpp> #include <boost/cstdint.hpp> // Includes ==================================================================== #include <hello.c> // Using ======================================================================= using namespace boost::python; // Declarations ================================================================ BOOST_PYTHON_OPAQUE_SPECIALIZED_TYPE_ID(PyObject) // Module ====================================================================== BOOST_PYTHON_MODULE(hello) { def("main", &main); def("testList", &testList, return_value_policy< return_opaque_pointer >()); } -- Qinfeng(Javen) Shi Research School of Information Sciences and Engineering Australian National University Locked Bag 8001 Canberra ACT 2601

1 0

Re: [C++-sig] Stuck on accessing numpy.ndarray in c extension
by Qinfeng(Javen) Shi Sept. 25, 2006

Sept. 25, 2006

My boost::python exporting code is as following: // Boost Includes ============================================================== #include <boost/python.hpp> #include <boost/cstdint.hpp> // Includes ==================================================================== #include "hello.c" // Using ======================================================================= using namespace boost::python; // Declarations ================================================================ // Module ====================================================================== BOOST_PYTHON_MODULE(hello) { def("main", &main); def("testArray", &testArray); } -- Qinfeng(Javen) Shi Research School of Information Sciences and Engineering Australian National University Locked Bag 8001 Canberra ACT 2601

2 1

Re: [C++-sig] Stuck on accessing numpy.ndarray in c extension
by Qinfeng(Javen) Shi Sept. 25, 2006

Sept. 25, 2006

No, I did not use raw_function for the export.I tried hello.testArray((c,)), it crashed. Then I used PyArray_Check(args) to check the input type, it crashed even when I passed a numpy.ndarray to it. void testArray(PyObject * args) { if(!(PyArray_Check(args))) { printf("args is not list type!\n"); return; } } >>> a = numpy.arange(25).reshape((5,5)); >>> rarray2 = hello.testArray(a,) Segmentation fault >>> a = numpy.arange(25).reshape((5,5)); >>> rarray2 = hello.testArray(a) Segmentation fault A *segmentation* *fault* occurs when a program attempts to access a memory location that it is not allowed to access, or attempts to access a memory location in a way that is not allowed. It seems my PyObject * args can not neither be acessed by PyArray_Check() nor by PyArg_ParseTuple(). I don't get it. -- Qinfeng(Javen) Shi Research School of Information Sciences and Engineering Australian National University Locked Bag 8001 Canberra ACT 2601

1 0

Py++ - problem with split_module and return_opaque_pointer-policy
by Ganssauge, Gottfried Sept. 25, 2006

Sept. 25, 2006

The return_value_policy<return_opaque_pointer> requires an additional macro call (BOOST_PYTHON_OPAQUE_SPECIALIZED_TYPE_ID) in the declaration section of a module. This can be added e.g. using module_builder_t.add_declaration_code(), and it works as long as you're generating the code using write_module(). In the moment you're using "split_module" to split your output, this scheme breaks, because BOOST_PYTHON_OPAQUE_SPECIALIZED_TYPE_ID is required in every translation unit using the opaque pointer type whose type_id is defined with that macro. Instead it is only generated into the main module. An example: test.hpp: ========= typedef struct opaque_ *opaque_pointer; opaque_pointer get_opaque(); test.py: ======== import os from pyplusplus import module_builder from pyplusplus.decl_wrappers import \ return_value_policy, \ return_opaque_pointer mb = module_builder.module_builder_t( ["test.hpp"] ) mb.add_declaration_code ("BOOST_PYTHON_OPAQUE_SPECIALIZED_TYPE_ID(opaque_)") mb.free_function (name = "get_opaque").call_policies = \ return_value_policy (return_opaque_pointer) mb.build_code_creator( module_name='test_opaque' ) mb.split_module( '.' ) When compiled with g++ -c -I/usr/include/python2.4 test_opaque*cpp this produces the following sermon: boost/python/type_id.hpp: In function `boost::python::type_info boost::python::type_id() [with T = opaque_]': boost/python/lvalue_from_pytype.hpp:23: instantiated from `boost::python::type_info boost::python::detail::extractor_type_id(T&(*)(U)) [with T = opaque_, U = boost::python::opaque_pointer_converter<opaque_*>::instance&]' boost/python/lvalue_from_pytype.hpp:88: instantiated from `boost::python::lvalue_from_pytype<Extractor, python_type>::lvalue_from_pytype() [with Extractor = boost::python::opaque_pointer_converter<opaque_*>, const PyTypeObject*python_type = ((const PyTypeObject*)(&boost::python::opaque_pointer_converter<opaque_*>::type_ object))]' boost/python/opaque_pointer_converter.hpp:116: instantiated from `void boost::python::opaque_pointer_converter<Pointer>::register_self() [with Pointer = opaque_*]' boost/python/opaque_pointer_converter.hpp:70: instantiated from `boost::python::opaque_pointer_converter<Pointer>::opaque_pointer_conver ter(const char*) [with Pointer = opaque_*]' boost/python/return_opaque_pointer.hpp:25: instantiated from `PyObject* boost::python::detail::opaque_conversion_holder<Pointer>::operator()(Poi nter) const [with Pointer = opaque_*]' boost/python/detail/invoke.hpp:75: instantiated from `PyObject* boost::python::detail::invoke(boost::python::detail::invoke_tag_< false, false>, const RC&, F&) [with RC = boost::python::detail::opaque_conversion_holder<opaque_*>, F = opaque_*(*)()]' boost/python/detail/caller.hpp:199: instantiated from `PyObject* boost::python::detail::caller_arity<0u>::impl<F, Policies, Sig>::operator()(PyObject*, PyObject*) [with F = opaque_*(*)(), Policies = boost::python::return_value_policy<boost::python::return_opaque_pointer, boost::python::default_call_policies>, Sig = boost::mpl::vector1<opaque_*>]' boost/python/object/py_function.hpp:38: instantiated from `PyObject* boost::python::objects::caller_py_function_impl<Caller>::operator()(PyOb ject*, PyObject*) [with Caller = boost::python::detail::caller<opaque_*(*)(), boost::python::return_value_policy<boost::python::return_opaque_pointer, boost::python::default_call_policies>, boost::mpl::vector1<opaque_*> >]' test_opaque_free_functions.pypp.cpp:21: instantiated from here boost/python/type_id.hpp:71: error: invalid use of undefined type `struct opaque_' test.hpp:1: error: forward declaration of `struct opaque_' Cheers, Gottfried

2 7

Stuck on accessing numpy.ndarray in c extension
by Qinfeng(Javen) Shi Sept. 25, 2006

Sept. 25, 2006

Dear *All *I got stuck on it on wrapping c++ code which need accept numpy.ndarray as argument. The numpy.version I am using is '1.0rc1'.* *(My previous question is too massy, so I revised it. Sorry if I borthered you!) I used two ways to access numpy.ndarray, but they all reported error. ----------------------------------------------------------------------------------- 1st way: void testArray(PyArrayObject * args) { } >>> hello.testArray(b) Traceback (most recent call last): File "<stdin>", line 1, in ? Boost.Python.ArgumentError: Python argument types in hello.testArray(numpy.ndarray) did not match C++ signature: testArray(PyArrayObject*) >>> ------------------------------------------------------------------------------------ 2nd way: void testArray(PyObject * args) { PyObject *input; PyArrayObject *array; if (!PyArg_ParseTuple(args, "O", &input)) printf("getting input failed!\n"); else printf("getting input sucess!\n"); } >>> import hello >>> import numpy >>> c = numpy.arange(25).reshape((5,5)) >>> d = hello.testArray(c); getting input failed! >>> d SystemError: new style getargs format but argument is not a tuple >>> Any suggestion will be appreciated. Thanks! -- Qinfeng(Javen) Shi Research School of Information Sciences and Engineering Australian National University Locked Bag 8001 Canberra ACT 2601

2 1

Pass the numpy.ndarray to c extension
by Qinfeng(Javen) Shi Sept. 25, 2006

Sept. 25, 2006

Thank for Dave Abrahams's suggestion to "numpy.ndarray did not match PyArrayObject *" problem. I didn't use the lvalue converter before. I will look up how to do it. Since what I really want to do is to pass the numpy.ndarray to c extension, so I started a new title. I find a way to pass the argument from the webpage: http://numpy.scipy.org/numpydoc/numpy-13.html . It uses PyArg_ParseTuple to transfer PyObject into PyArrayObject. I implemented two functions with PyArg_ParseTuple(), but they all reported error. /***************c extension*********/ void testArray(PyObject * args) { PyObject *input; PyArrayObject *array; if (!PyArg_ParseTuple(args, "O", &input)) printf("getting input failed!\n"); else printf("getting input sucess!\n"); array = (PyArrayObject *) PyArray_ContiguousFromObject(input, PyArray_INT, 0, 3); if (array == NULL) printf("getting array failed!\n"); else printf("getting array sucess!\n"); } static PyObject * trace(PyObject *self, PyObject *args) { PyObject *input; PyArrayObject *array; double sum; int i, n; if (!PyArg_ParseTuple(args, "O", &input)) return NULL; array = (PyArrayObject *) PyArray_ContiguousFromObject(input, PyArray_DOUBLE, 2, 2); if (array == NULL) return NULL; n = array->dimensions[0]; if (n > array->dimensions[1]) n = array->dimensions[1]; sum = 0.; for (i = 0; i < n; i++) sum += *(double *)(array->data + i*array->strides[0] + i*array->strides[1]); Py_DECREF(array); return PyFloat_FromDouble(sum); } /************error report************/ >>> import hello >>> import numpy >>> c = numpy.arange(25).reshape((5,5)) >>> print c [[ 0 1 2 3 4] [ 5 6 7 8 9] [10 11 12 13 14] [15 16 17 18 19] [20 21 22 23 24]] >>> b = hello.trace(c,c) >>> b SystemError: new style getargs format but argument is not a tuple >>> d = hello.testArray(c); getting input failed! >>> d SystemError: new style getargs format but argument is not a tuple >>> -- Qinfeng(Javen) Shi Research School of Information Sciences and Engineering Australian National University Locked Bag 8001 Canberra ACT 2601

1 0

Opportunities at Naughty Dog...
by CP Sept. 24, 2006

Sept. 24, 2006

Dear Mr. Summers, I hope to become one of Naughty Dogs employees one day sadly I am not old enought yet, but before you delete this message like your company did when I e-mailed them 1-2 months back just listen to my question and get back to me. I want to know if there is going to be another Jak game coming because the game in development "Big" just doesn't look like it is for me. So is there goning to be another Jak game? That is all I want to know. When I reach college I hope to become a content manager like Sony's own Gene Strocco. I want to study at mabe USC and go on to work at Nauhty Dog after I get my degree. Thank you for listening, Chris

1 0