David Hewitt

If I recall correctly, this is a good summary of why we didn't support the `abi3` feature for non-extension modules. We found that `libpython3.so` rarely (if ever?) exists, which prevents...

Yep, exactly. > Adding `derive_gc = false` just because `PyGcIntegration` is not implemented on `usize` would be sad. I think we would derive `PyGcIntegration` on `usize` and make it a...

> If we do that doesn't it mean we require users to make sure that `PyGcIntegration` is implemented on all types they use as `pyclass` fields? It might lead to...

Thanks for this suggestion. I've often wanted such a constructor generated for me. In combination with #1375, binding pod structs would be very convenient. I don't think we want to...

It feels to me like we should consider changing `PyBuffer::drop` to be more like `Py::drop` where we don't try to automatically acquire the GIL (this can in theory lead to...

True; it's probably correct to add a check that the interpreter is initialized somewhere in that machinery. I think it's complicated a bit by the possibility of finalizing and restarting...

I added full build, if you want to fixup merge conflict we can see what initial results are.

> > You should bump cpython’s `max-version` in `pyo3-ffi/cargo.toml` to 1.15. > > cpython 3.15 C-API is I think still moving, wouldn't it better to keep the error message and...

Do we need to wait for 3.15 to mature before investing effort in this?

Yes absolutely! I hadn't really made much progress with this, however I started some time ago playing around with such a macro in https://github.com/davidhewitt/pyo3-pytypes Perhaps you'd be interested in helping...