[C++-sig] wrapping the PyObject_Call() interface
bourdenas at gmail.com
Sat Jul 26 19:07:30 CEST 2008
Thanks that works fine.
Though I'd like to ask you whether there is any reason for unary operator *
to work only with boost::python::tuple and not with boost::python::list. At
first I used the latter and I got a python exception that while the
functions I was calling was requiring N arguments, it was provided with 0.
It was also the case of a bound member function, meaning that at least the
self argument was already embedded in the boost::python::object I was
calling. When I converted the list to a tuple the call run smoothly.
Is this patch going to be in the 1.36.0 release? If not are there any plans
for which release it will be included in?
On Sat, Jul 26, 2008 at 1:46 PM, Stefan Seefeld <seefeld at sympatico.ca>wrote:
> Themistoklis Bourdenas wrote:
>> Hi, I was looking in the boost.python for a wrapper of the PyObject_Call()
>> func but couldn't find anything. Did I missed it or has it not been
>> implemented yet? In essence I need to call functions in python by providing
>> a collection (either stl or boost.python collection) of
>> boost::python::object instances instead of giving the arguments in the
>> traditional way.
>> Any ideas, or should I use directly PyObject_Call()?
> I have a patch for this (https://svn.boost.org/trac/boost/ticket/1316),
> but it requires a final review. You may apply it to your sources locally.
> ...ich hab' noch einen Koffer in Berlin...
> C++-sig mailing list
> C++-sig at python.org <C%2B%2B-sig at python.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Cplusplus-sig