The IDENTIFIERS list in Tools/scripts/generate_global_objects.py is a slight burden

(This is partly inspired by gh-94706.)

In generate_global_objects.py, iter_global_strings() detects global strings by looking for _Py_ID() and _Py_DECLARE_STR() in the C source files. In some places those macros are used indirectly, which means the corresponding strings won't be detected by iter_global_strings().

Currently we manually add such strings to the IDENTIFIERS list at the top of the script. Before we added the discovery mechanism in iter_global_strings(), basically all the static strings were in this list. However, we found that there were several maintenance/development downsides to the manual list, so we added iter_global_strings(). At the time we didn't take the extra step of automating discovery of indirectly used names. We should address this.

CC @kumaraditya303

Commencez par Tools/scripts/generate_global_objects.py, en vous concentrant sur iter_global_strings() et sur la liste IDENTIFIERS maintenue manuellement. Suivez la manière dont le script parcourt les fichiers sources C à la recherche de _Py_ID() et de _Py_DECLARE_STR(), puis déterminez comment les noms utilisés indirectement peuvent être détectés. Le travail est terminé lorsque les chaînes globales utilisées indirectement ne nécessitent plus d’ajouts manuels et que la génération reste correcte.