Inconsistent handling of the modulo argument for ternary pow() (pure-Python vs extension)

Bug report

Bug description:

This is a follow-up of the https://github.com/python/cpython/issues/130104.

An example with the stdlib:

>>> import decimal, _pydecimal
>>> pow(2, 3, decimal.Decimal(4))
Decimal('0')
>>> pow(2, 3, _pydecimal.Decimal(4))
Traceback (most recent call last):
  File "<python-input-5>", line 1, in <module>
    pow(2, 3, _pydecimal.Decimal(4))
    ~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: unsupported operand type(s) for ** or pow(): 'int', 'int', 'Decimal'

IIUIC, pow() it just calls the __pow__() for the third argument with original order of ops as a fallback. So, we can just do something like this:

diff --git a/Objects/typeobject.c b/Objects/typeobject.c
index 14bc5a4bc4..911c890fcb 100644
--- a/Objects/typeobject.c
+++ b/Objects/typeobject.c
@@ -10377,7 +10377,27 @@ slot_nb_power(PyObject *self, PyObject *other, PyObject *modulus)
         stack[2] = modulus;
         return vectorcall_maybe(tstate, &_Py_ID(__rpow__), stack, 3);
     }
-    Py_RETURN_NOTIMPLEMENTED;
+    stack[0] = self;
+    stack[1] = other;
+    stack[2] = modulus;
+
+    _PyCStackRef cref;
+    _PyThreadState_PushCStackRef(tstate, &cref);
+    int unbound = lookup_maybe_method(modulus, &_Py_ID(__pow__), &cref.ref);
+    PyObject *func = PyStackRef_AsPyObjectBorrow(cref.ref);
+
+    if (func == NULL) {
+        _PyThreadState_PopCStackRef(tstate, &cref);
+        if (!PyErr_Occurred()) {
+            Py_RETURN_NOTIMPLEMENTED;
+        }
+        return NULL;
+    }
+
+    PyObject *retval = vectorcall_unbound(tstate, unbound, func, stack, 3);
+
+    _PyThreadState_PopCStackRef(tstate, &cref);
+    return retval;
 }
 
 SLOT0(slot_nb_negative, __neg__)

Full patch: https://github.com/skirpichev/cpython/pull/9

CPython versions tested on:

CPython main branch

Operating systems tested on:

No response

Beginne in Objects/typeobject.c bei slot_nb_power und reproduziere die decimal/_pydecimal-Beispiele aus dem Bericht auf einem CPython-main-Build. Vergleiche das Verhalten von ternary pow() zwischen den Pure-Python- und den Extension-Implementierungen; abgeschlossen ist die Aufgabe, wenn beide das Modulo-Argument konsistent behandeln, ohne das bestehende Fallback-Verhalten zu beeinträchtigen.