managed by a Python object. When that Python object is
          destroyed, our pointer dangles. The problem is particularly bad when the
          ResultType is char const* - the corresponding Python String object is typically
          uniquely-referenced, meaning that the pointer dangles as soon as call&lt;char
          const*&gt;(...) returns.
        </p>
<p>
          The old Boost.Python v1 deals with this issue by refusing to compile any
          uses of call&lt;char const*&gt;(), but this goes bo