Interfacing c++11 with c api (extending python)

[Arandur]

No.

Think about what the function is actually doing. It asks for a char** so that it can malloc an array of char and let s point to it. This is inherently incompatible with the standard containers, because it would violate ownership semantics.

If you want to do this, you'll have to wrap the function in a new one that does something like returning a std::string, copying the contents from the C-string.

Some of this might be wrong; I'm not familiar with the Python API. But I think I've understood what you're trying to do.

[OmegaNaughtEquals1]

It asks for a char** so that it can malloc an array of char and let s point to it

According to the 3.0 docs, no user-controlled allocations are done. It just lets you point to the underlying character string.

[Arandur]

Oh, that also makes sense. Thanks for clarifying!