It's not a keyword, neither in C nor Python. It's just a way to indicate that it is logically a type/class, rather than a function or method slot or the like. type is a built-in class in Python (all Python classes are instances of type, directly or indirectly), but it's not a reserved keyword; you could name a variable type if you wanted (though you'd cut off access to the original type within that scope).
In the absolute most modern versions of Python (3.12+), type is technically a "soft keyword" (meaning it's only a keyword in a specific narrow syntactic context, but usable arbitrarily elsewhere) used to enable lazy evaluation for types used in type annotations, but that usage came long after the docs began using type to indicate class types.
PEP 695 – Type Parameter Syntax
Is it safe to use the python word "type" in my code? - Stack Overflow
Introduce type keyword for type only imports - Ideas - Discussions on Python.org
Use type keyword for defining NewTypes in Non-Generic types - Ideas - Discussions on Python.org
It's not a keyword, neither in C nor Python. It's just a way to indicate that it is logically a type/class, rather than a function or method slot or the like. type is a built-in class in Python (all Python classes are instances of type, directly or indirectly), but it's not a reserved keyword; you could name a variable type if you wanted (though you'd cut off access to the original type within that scope).
In the absolute most modern versions of Python (3.12+), type is technically a "soft keyword" (meaning it's only a keyword in a specific narrow syntactic context, but usable arbitrarily elsewhere) used to enable lazy evaluation for types used in type annotations, but that usage came long after the docs began using type to indicate class types.
What appears as type means different things depending on whether you're looking at documentation intended for C or Python.
The documentation source you're looking at is at cpython/Doc/c-api/type.rst, where it is written as c:type:: PyTypeObject. This is for C code, and is Sphinx syntax, which is documented here:
.. c:type:: typedef-like declaration
.. c:type:: nameDescribes a C type, either as a typedef, or the alias for an unspecified type.
This indicates that PyTypeObject is either a name of a C typedef or some existing struct.
If you see type XYZ in docs intended for Python code, it would actually be py:type: in the documentation source, which only refers to the name of a Python type alias, and never the name of a class.
What is rendered as type XYZ mirrors the type statement declaration syntax, and here, in Python source code type is actually a soft keyword.
Using type as a keyword argument to a function will mask the built-in function "type" within the scope of the function. So while doing so does not raise a SyntaxError, it is not considered good practice, and I would avoid doing so.
Neither. It's not a reserved word (a list of which can be found at http://docs.python.org/reference/lexical_analysis.html#keywords ), but it's generally a bad idea to shadow any builtin.