[C++-sig] to_python converter and make_getter
Jim Bosch
talljimbo at gmail.com
Tue Jan 22 23:27:01 CET 2013
On 01/22/2013 04:18 PM, Michael Wild wrote:
> Dear all
>
> I have defined a to_python converter following
> http://misspent.wordpress.com/2009/09/27/how-to-write-boost-python-converters.
> Everything is fine and dandy, however what bugs me is having to specify
> a return_value_policy<return_by_value>() for every make_getter call.
> Looking through the sources it seems that I should be able to tell
> make_getter what the default policy should be by somehow specializing
> default_member_getter_policy and default_datum_getter_policy. However,
> is this the right way to go, or should I attack the problem at a lower
> level, e.g. by specializing default_getter_by_ref? Or should I directly
> specialize make_getter?
>
Could you provide a little more information about what you're trying to
do and what the error is? I'm surprised that you're having to specify a
call-policy manually for return-by-value; I've used by-value to_python
converters plenty of times without ever having to do that.
Jim
More information about the Cplusplus-sig
mailing list