any reason Py::from_owned_ptr_or_err is unsafe but all function it calls are safe?

[trim21]

        unsafe {
            return Py::from_owned_ptr_or_err(self.py, ptr);
        }

equal to

        return match NonNull::new(ptr) {
            Some(nonnull_ptr) => Ok(Py(nonnull_ptr, PhantomData)),
            None => Err(PyErr::fetch(self.py)),
        };

[adamreichold]

Being non-null is not sufficient for a pointer to point to a valid object in the Python heap. It could be dangling or not point into the Python heap at all.

[trim21]

thanks