##// END OF EJS Templates
rust-pyo3: intermediate ProxyIndex extraction...
Georges Racinet -
r53424:64a61804 default
parent child Browse files
Show More
@@ -1,186 +1,195
1 1 //! This module takes care of all conversions involving `rusthg` (hg-cpython)
2 2 //! objects in the PyO3 call context.
3 3 //!
4 4 //! For source code clarity, we only import (`use`) [`cpython`] traits and not
5 5 //! any of its data objects. We are instead using full qualifiers, such as
6 6 //! `cpython::PyObject`, and believe that the added heaviness is an acceptatble
7 7 //! price to pay to avoid confusion.
8 8 //!
9 9 //! Also it, is customary in [`cpython`] to label the GIL lifetime as `'p`,
10 10 //! whereas it is `'py` in PyO3 context. We keep both these conventions in
11 11 //! the arguments side of function signatures when they are not simply elided.
12 12 use pyo3::exceptions::PyTypeError;
13 13 use pyo3::prelude::*;
14 14
15 15 use cpython::ObjectProtocol;
16 16 use cpython::PythonObject;
17 17 use lazy_static::lazy_static;
18 18
19 19 use hg::revlog::index::Index as CoreIndex;
20 20 use rusthg::revlog::{InnerRevlog, PySharedIndex};
21 21
22 22 /// Force cpython's GIL handle with the appropriate lifetime
23 23 ///
24 24 /// In `pyo3`, the fact that we have the GIL is expressed by the lifetime of
25 25 /// the incoming [`Bound`] smart pointer. We therefore simply instantiate
26 26 /// the `cpython` handle and coerce its lifetime by the function signature.
27 27 ///
28 28 /// Reacquiring the GIL is also a possible alternative, as the CPython
29 29 /// documentation explicitely states that "recursive calls are allowed"
30 30 /// (we interpret that as saying that acquiring the GIL within a thread that
31 31 /// already has it works) *as long as it is properly released*
32 32 /// reference:
33 33 /// <https://docs.python.org/3.8/c-api/init.html#c.PyGILState_Ensure>
34 34 pub(crate) fn cpython_handle<'py, T>(
35 35 _bound: &Bound<'py, T>,
36 36 ) -> cpython::Python<'py> {
37 37 // safety: this is safe because the returned object has the 'py lifetime
38 38 unsafe { cpython::Python::assume_gil_acquired() }
39 39 }
40 40
41 41 /// Force PyO3 GIL handle from cpython's.
42 42 ///
43 43 /// Very similar to [`cpython_handle`]
44 44 pub fn pyo3_handle(_py: cpython::Python<'_>) -> Python<'_> {
45 45 // safety: this is safe because the returned object has the same lifetime
46 46 // as the incoming object.
47 47 unsafe { Python::assume_gil_acquired() }
48 48 }
49 49
50 50 /// Convert a PyO3 [`PyObject`] into a [`cpython::PyObject`]
51 51 ///
52 52 /// During this process, the reference count is increased, then decreased.
53 53 /// This means that the GIL (symbolized by the lifetime on the `obj`
54 54 /// argument) is needed.
55 55 ///
56 56 /// We could make something perhaps more handy by simply stealing the
57 57 /// pointer, forgetting the incoming and then implement `From` with "newtype".
58 58 /// It would be worth the effort for a generic cpython-to-pyo3 crate, perhaps
59 59 /// not for the current endeavour.
60 60 pub(crate) fn to_cpython_py_object<'py>(
61 61 obj: &Bound<'py, PyAny>,
62 62 ) -> (cpython::Python<'py>, cpython::PyObject) {
63 63 let py = cpython_handle(obj);
64 64 // public alias of the private cpython::fii::PyObject (!)
65 65 let raw = obj.as_ptr() as *mut python3_sys::PyObject;
66 66 // both pyo3 and rust-cpython will decrement the refcount on drop.
67 67 // If we use from_owned_ptr, that's a segfault.
68 68 (py, unsafe { cpython::PyObject::from_borrowed_ptr(py, raw) })
69 69 }
70 70
71 71 /// Convert a [`cpython::PyObject`] into a PyO3 [`PyObject`]
72 72 ///
73 73 /// During this process, the reference count is increased, then decreased.
74 74 /// This means that the GIL (symbolized by the PyO3 [`Python`] handle is
75 75 /// needed.
76 76 ///
77 77 /// We could make something perhaps more handy by simply stealing the
78 78 /// pointer, forgetting the incoming and then implement `From` with "newtype".
79 79 /// It would be worth the effort for a generic cpython-to-pyo3 crate, perhaps
80 80 /// not for the current endeavour.
81 81 pub(crate) fn from_cpython_py_object(
82 82 py: Python<'_>,
83 83 obj: cpython::PyObject,
84 84 ) -> PyObject {
85 85 let raw = obj.as_ptr() as *mut pyo3::ffi::PyObject;
86 86 unsafe { Py::from_borrowed_ptr(py, raw) }
87 87 }
88 88
89 89 /// Convert [`cpython::PyErr`] into [`pyo3::PyErr`]
90 90 ///
91 91 /// The exception class remains the same as the original exception,
92 92 /// hence if it is also defined in another dylib based on `cpython` crate,
93 93 /// it will need to be converted to be downcasted in this crate.
94 94 pub(crate) fn from_cpython_pyerr(
95 95 py: cpython::Python<'_>,
96 96 mut e: cpython::PyErr,
97 97 ) -> PyErr {
98 98 let pyo3_py = pyo3_handle(py);
99 99 let cpython_exc_obj = e.instance(py);
100 100 let pyo3_exc_obj = from_cpython_py_object(pyo3_py, cpython_exc_obj);
101 101 PyErr::from_value(pyo3_exc_obj.into_bound(pyo3_py))
102 102 }
103 103
104 104 /// Retrieve the PyType for objects from the `mercurial.rustext` crate.
105 105 fn retrieve_cpython_py_type(
106 106 submodule_name: &str,
107 107 type_name: &str,
108 108 ) -> cpython::PyResult<cpython::PyType> {
109 109 let guard = cpython::Python::acquire_gil();
110 110 let py = guard.python();
111 111 let module = py.import(&format!("mercurial.rustext.{submodule_name}"))?;
112 112 module.get(py, type_name)?.extract::<cpython::PyType>(py)
113 113 }
114 114
115 115 lazy_static! {
116 116 static ref INNER_REVLOG_PY_TYPE: cpython::PyType = {
117 117 retrieve_cpython_py_type("revlog", "InnerRevlog")
118 118 .expect("Could not import InnerRevlog in Python")
119 119 };
120 120 }
121 121
122 122 /// Downcast [`InnerRevlog`], with the appropriate Python type checking.
123 123 ///
124 124 /// The PyType object representing the `InnerRevlog` Python class is not the
125 125 /// the same in this dylib as it is in the `mercurial.rustext` module.
126 126 /// This is because the code created with the [`cpython::py_class!`]
127 127 /// macro is itself duplicated in both dylibs. In the case of this crate, this
128 128 /// happens by linking to the [`rusthg`] crate and provides the `InnerRevlog`
129 129 /// that is visible from this crate. The `InnerRevlog::get_type` associated
130 130 /// function turns out to return a `static mut` (look for `TYPE_OBJECT` in
131 131 /// `py_class_impl3.rs`), which obviously is different in both dylibs.
132 132 ///
133 133 /// The consequence of that is that downcasting an `InnerRevlog` originally
134 134 /// from the `mecurial.rustext` module to our `InnerRevlog` cannot be done with
135 135 /// the usual `extract::<InnerRevlog>(py)`, as it would perform the type
136 136 /// checking with the `PyType` that is embedded in `mercurial.pyo3_rustext`.
137 137 /// We must check the `PyType` that is within `mercurial.rustext` instead.
138 138 /// This is what this function does.
139 139 fn extract_inner_revlog(
140 140 py: cpython::Python,
141 141 inner_revlog: cpython::PyObject,
142 142 ) -> PyResult<InnerRevlog> {
143 143 if !(*INNER_REVLOG_PY_TYPE).is_instance(py, &inner_revlog) {
144 144 return Err(PyTypeError::new_err("Not an InnerRevlog instance"));
145 145 }
146 146 // Safety: this is safe because we checked the PyType already, with the
147 147 // value embedded in `mercurial.rustext`.
148 148 Ok(unsafe { InnerRevlog::unchecked_downcast_from(inner_revlog) })
149 149 }
150 150
151 151 /// This is similar to [`rusthg.py_rust_index_to_graph`], with difference in
152 152 /// how we retrieve the [`InnerRevlog`].
153 153 pub fn py_rust_index_to_graph(
154 154 py: cpython::Python,
155 155 index_proxy: cpython::PyObject,
156 156 ) -> PyResult<cpython::UnsafePyLeaked<PySharedIndex>> {
157 157 let inner_revlog = extract_inner_revlog(
158 158 py,
159 159 index_proxy
160 160 .getattr(py, "inner")
161 161 .map_err(|e| from_cpython_pyerr(py, e))?,
162 162 )?;
163 163
164 164 let leaked = inner_revlog.pub_inner(py).leak_immutable();
165 165 // Safety: we don't leak the "faked" reference out of the `UnsafePyLeaked`
166 166 Ok(unsafe { leaked.map(py, |idx| PySharedIndex { inner: &idx.index }) })
167 167 }
168 168
169 pub(crate) fn proxy_index_py_leak<'py>(
170 index_proxy: &Bound<'py, PyAny>,
171 ) -> PyResult<(cpython::Python<'py>, cpython::UnsafePyLeaked<PySharedIndex>)> {
172 let (py, idx_proxy) = to_cpython_py_object(index_proxy);
173 let py_leaked = py_rust_index_to_graph(py, idx_proxy)?;
174 Ok((py, py_leaked))
175 }
176
169 177 /// Full extraction of the proxy index object as received in PyO3 to a
170 178 /// [`CoreIndex`] reference.
171 179 ///
172 /// The safety invariants to maintain are those of the underlying
180 /// # Safety
181 ///
182 /// The invariants to maintain are those of the underlying
173 183 /// [`UnsafePyLeaked::try_borrow`]: the caller must not leak the inner
174 184 /// reference.
175 185 pub(crate) unsafe fn proxy_index_extract<'py>(
176 186 index_proxy: &Bound<'py, PyAny>,
177 187 ) -> PyResult<&'py CoreIndex> {
178 let (py, idx_proxy) = to_cpython_py_object(index_proxy);
179 let py_leaked = py_rust_index_to_graph(py, idx_proxy)?;
188 let (py, py_leaked) = proxy_index_py_leak(index_proxy)?;
180 189 let py_shared = &*unsafe {
181 190 py_leaked
182 191 .try_borrow(py)
183 192 .map_err(|e| from_cpython_pyerr(py, e))?
184 193 };
185 194 Ok(py_shared.inner)
186 195 }
General Comments 0
You need to be logged in to leave comments. Login now