David Hewitt
David Hewitt
Just a bit of playing around to remove `PyMethodDefType` by making types in `pyo3-macros-backend` a bit more concrete and growing the `PyClassItems` struct to have explicit `class_attributes`, `getters` and `setters`...
A wip implementation of proposal in #2193. Still a long way to go. Not worth reviewing yet, posting just so interested folks can have eyes on it.
As originally posted on Gitter by @microgravitas: > Hi y'all! Can anyone point me to an example of how to implement an Python iterator which does not copy the whole...
This issue is a placeholder issue which I'd like to use to keep track of what we need to do to support `async fn` for `#[pyfunction]` (and `#[pymethods]`). While this...
I don't think it's possible for `#[new]` in PyO3 to return an existing object (at the moment), though it really should be. _Originally posted by @davidhewitt in https://github.com/PyO3/pyo3/discussions/2382#discussioncomment-2765288_
Implements using `#[pymodule]` directly on modules. Allows importing other wrapped items with a `#[pyo3] use foo;`. (Builds on #2366 to do this.) Allows having a `#[pymodule_init]` function to run arbitrary...
Inspired by https://github.com/PyO3/pyo3/pull/2269#issuecomment-1087901951, this is an issue to track all of the places which we know need to change for full PEP 489 compatibility (draft implementation in #2245). The latest...
Like we have `#[pyclass(unsendable)]` to opt-out of `Send`, many users will not want their pyclass to be mutable. It would be nice if we could allow them to opt-out of...
This is throwing out a concept that I've been pondering for a while to progress with the design of the to-python conversion traits. It replaces `IntoPy` generic trait with a...
In comment to `Py::as_bytes`: ---- I think there's a few other immutable types like `str` and `tuple` which I guess can also have treatment like this where `py` is necessary...