Creating PyObject* in external code about go-python HOT 5 CLOSED

I can of course expose togo - which I would probably expose as:

func PyObject_FromVoidPtr(ptr unsafe.Pointer) *PyObject { ... }

but, as you mentionned numpy, perhaps a more useful API to expose would be capsules ?
https://docs.python.org/2/c-api/capsule.html#capsules

(BTW: any pointer to your numpy-based+go project? color me interested!)

from go-python.

I am/was not familiar with capsules. AFAICT, however, this is an orthogonal concept, no? I still need SimpleNewFromData from NumPy---my use case is the same as Travis', here:

http://blog.enthought.com/python/numpy/simplified-creation-of-numpy-arrays-from-pre-allocated-memory/

but he's unfortunately using the CObject way there. Charles Harris explicitly notes that NumPy uses the CObject method internally:

https://bugzilla.redhat.com/show_bug.cgi?id=623857#c3

So perhaps that forces our hand to use the old way? It is (very) possible that I'm misunderstanding how this would work with capsules, though. Would welcome some education on that.

Re: the project, the code is here:

https://github.com/tfogal/visdebug

but there's far too much to grok. We're preparing a manuscript to submit academically, but I'm too embarrassed about its current state to post it publicly. Happy to send it to you via email, though.

from go-python.

I proposed PyCapsules because PyCObject are deprecated in 2.7, but I can as easily wrap PyCObject. would that work for you ?

but, ok. if somebody were to wrap, say, numpy with cgo, she would still need a way to convert an unsafe.Pointer into a python.PyObject.
so... I'll start with exposing togo via PyObject_FromVoidPtr.

from go-python.

Sounds great, thanks!

from go-python.

fixed with 06cbd38

from go-python.