PEP 737 – Unify type name formatting

@vstinner - The 2024 Steering Council discussed PEP 737 today, so with that hat on, I’d like to share our feedback. First of all, thank you for putting this PEP together along with the associated PR.

We can see the usefulness of the C API changes proposed by the PEP and would likely accept those changes as is.

We see less justification for the Python level changes. We especially question the need for __fully_qualified_name__. As a side note, we prefer __fullname__ as previously suggested in an earlier post although that is moot if we do not accept the Python level changes.

Our question to Victor is: would you be willing to update the PEP to propose only the C API changes, deferring the Python changes to some separate, future PEP?

2 Likes