No, definitely not, because of the nature of the content. That page’s introduction reads:
This article contains several guidelines and suggestions for programmers working in and with the GNOME stack. This is intended for programmers to know about the development processes, conventions and philosophies behind GNOME applications and the stack of libraries supporting them.
gnome* modules in my Fedora 31 machine’s
So, while there are language bindings that export GNOME APIs to other languages, that doesn’t mean the GNOME coding guidelines apply to those languages, or that the GNOME developers would be a particularly good source of Python coding advice.
Coding advice for GNOME’s Python APIs would require someone to write it, specifically in the context of that language, and such a document would end up having almost no discernible relationship to the one written (quite a long time ago) by and for the core GNOME C-language developers.
But, really, it’ll be far more productive to take good Python coding advice (there’s plenty out there, starting with the style guidance found in the venerable PEP8 itself) and apply it to writing Python code that works with the GNOME Python APIs, than it would be to translate GNOME-centric C coding advice into (inevitably poorer) Python coding advice.