From 3edde98bb1a541d97f7113a77b30c35fc93ce3dc Mon Sep 17 00:00:00 2001
From: dot <dot@youknowone.org>
Date: Sat, 10 Oct 2026 20:15:54 +0900
Subject: [PATCH] Drop the legacy abi3-only PyCFunction_Call export

Follow up on #9055: RustPython targets abi3t, which does not require this legacy binary-compatibility entry point.

Assisted-by: OpenAI Codex:model identifier unavailable
---
 crates/capi/src/methodobject.rs | 10 ----------
 1 file changed, 10 deletions(-)

diff --git a/crates/capi/src/methodobject.rs b/crates/capi/src/methodobject.rs
index 3b0795deeb3..2e82c5e9daa 100644
--- a/crates/capi/src/methodobject.rs
+++ b/crates/capi/src/methodobject.rs
@@ -11,16 +11,6 @@ use rustpython_vm::{AsObject, PyObjectRef, PyRef, PyResult, VirtualMachine};
 define_py_check!(fn PyCFunction_Check, types.builtin_function_or_method_type);
 define_py_check!(exact fn PyCFunction_CheckExact, types.builtin_function_or_method_type);
 
-// Removed from the public API in 3.13, but retained in the stable ABI.
-#[unsafe(no_mangle)]
-pub unsafe extern "C" fn PyCFunction_Call(
-    callable: *mut PyObject,
-    args: *mut PyObject,
-    kwargs: *mut PyObject,
-) -> *mut PyObject {
-    unsafe { crate::abstract_::PyObject_Call(callable, args, kwargs) }
-}
-
 #[repr(C)]
 #[derive(Debug)]
 pub struct PyMethodDef {