From 40ac28e8e835110b579a56cbb64b3aaecbb7764d Mon Sep 17 00:00:00 2001
From: Michael Schroeder <mls@suse.de>
Date: Tue, 13 Feb 2024 16:33:48 +0100
Subject: [PATCH] Always use PyObject_Call as suggested by Jan Kolarik

PyObject_Call is available since python 2.2
---
 bindings/solv.i | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/bindings/solv.i b/bindings/solv.i
index 372c862a6..16333059d 100644
--- a/bindings/solv.i
+++ b/bindings/solv.i
@@ -1729,11 +1729,7 @@ returnself(matchsolvable)
   SWIGINTERN int loadcallback(Pool *pool, Repodata *data, void *d) {
     XRepodata *xd = new_XRepodata(data->repo, data->repodataid);
     PyObject *args = Py_BuildValue("(O)", SWIG_NewPointerObj(SWIG_as_voidptr(xd), SWIGTYPE_p_XRepodata, SWIG_POINTER_OWN | 0));
-#if PY_VERSION_HEX >= 0x03000000
     PyObject *result = PyObject_Call((PyObject *)d, args, NULL);
-#else
-    PyObject *result = PyEval_CallObject((PyObject *)d, args);
-#endif
 
     int ecode = 0;
     int vresult = 0;