You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Code that uses pybind11 often has to interoperate with legacy code that uses THPObjectPtr. Thus, there are a number of common things that one might have to do, e.g., interconvert between PyObject*, THPObjectPtr, py::handle and py::object. We should document pave the cowpaths, and eventually get rid of THPObjectPtr entirely (if possible.)
The text was updated successfully, but these errors were encountered:
Let's not go too far too quickly. We still haven't fully evaluated pybind. While the quality of bindings doesn't really matter for the JIT, because it's not a hot spot, we need to maintain the lowest possible overhead for tensor/autograd bindings.
Code that uses pybind11 often has to interoperate with legacy code that uses THPObjectPtr. Thus, there are a number of common things that one might have to do, e.g., interconvert between
PyObject*
,THPObjectPtr
,py::handle
andpy::object
. We shoulddocumentpave the cowpaths, and eventually get rid of THPObjectPtr entirely (if possible.)The text was updated successfully, but these errors were encountered: