Daniel Grunwald

It doesn't make sense to reduce the size of these unsafe blocks -- the code that you moved outside the blocks is still relevant to their safety and needs to...

We should wait for the RC which typically is ABI-compatible with the final release. Can you rebase your branch onto the current master? I've fixed the failure with Rust 1.41.1.

rust-cpython will (via [this build script](https://github.com/dgrunwald/rust-cpython/blob/master/python3-sys/build.rs)) ask your current Python interpreter for its `sys.exec_prefix`. It'll then look for `python39.lib` relative to that directory. Which Python interpreter gets asked can be...

Both C and Rust use a `u32` to access that field, so they should both use the same byte order. I guess the problem is rather that s390x uses a...

The python3-sys build script asks your currently installed python interpreter for its compilation flags, so that python3-sys can be compiled with a compatible ABI. That approach won't really work when...

> before it has dropped the RefCell (and thus definitely before it has dropped the GIL) The part in the parentheses is not a valid conclusion. Every function taking a...

Note that this applies not just to `GILProtected`, but also to the data members of a `py_class!`.

Any call into the Python interpreter could do one of the following: * release the last reference to an object with a `__del__` implemented in Python (-> the Python code...

`GILProtected` can still work if the Python code takes care not to call into the extension module from multiple threads concurrently. I don't think this is a safety problem as...

The problem is that it is unclear what `().to_py_object()` should return: In the context of a method return value, it should return `None`. But in other contexts (e.g. specifying arguments...