PyPySide: Rename interface functions and classes to simplify debugging

The names of certain interface functions are not always
following a simple scheme. Especially it is not easy
to see immediately if we are dealing with a method
of SbkObjectType or SbkObject

Do a few renamings to simplify debugging and make the code
easier to understand. When a function is used in a type spec
and there is no other important reason, it should be named
like

    {Py_<tpname>: reinterpret_cast<void *>(<TypeName>_<tpname>)},

Rename also all type functions ending on "TypeF()" to end
in "_TypeF()". This is not always the case.

Examples:
    SbkObjectTpNew -> SbkObject_tp_new
    SbkObjecttypeTpNew -> SbkObjectType_tp_new

    PyClassPropertyTypeF -> PyClassProperty_TypeF

Task-number: PYSIDE-535
Change-Id: Icbd118852f2ee732b55d944ed57c7a8ef7d26139
Reviewed-by: Friedemann Kleint <[email protected]>

1 files changed, 1 insertions, 1 deletions

diff --git a/sources/pyside6/libpyside/feature_select.cpp b/sources/pyside6/libpyside/feature_select.cpp
index f0cc4f416..ec7798960 100644
--- a/sources/pyside6/libpyside/feature_select.cpp
+++ b/sources/pyside6/libpyside/feature_select.cpp
@@ -574,7 +574,7 @@ static PyObject *createProperty(PyTypeObject *type, PyObject *getter, PyObject *
         setter = Py_None;
     auto ptype = &PyProperty_Type;
     if (Py_TYPE(getter) == PepStaticMethod_TypePtr) {
-        ptype = PyClassPropertyTypeF();
+        ptype = PyClassProperty_TypeF();
         getter = modifyStaticToClassMethod(type, getter);
         if (setter != Py_None)
             setter = modifyStaticToClassMethod(type, setter);