Attribute cache silently disabled after 1000 class edit, leading to poor performance

Bug report

Bug description:

After the changes from https://github.com/python/cpython/pull/114900 modifying a class more than 1000 times causes the attribute cache to be permanently disabled for that class. This was done to solve a crash when a class is modified more than 2**32 times ( https://github.com/python/cpython/issues/113462 )

It seems this number (1000) is too low for some real case applications.

I initially observed this as a ~50% performance regression in ERP5 performance tests when updating from python3.11 to python3.13. ERP5 is an application where classes are generated dynamically based on some configuration and some classes are modified more than 1000 times in the "normal" generation process.

This seems to also affect odoo, another ERP application, for this they resorted to using ctypes to reset the class version attribute ( https://github.com/odoo/odoo/pull/275640 )

My suggestion would be to use a much higher number before disabling the cache, 1000 is low.

CPython versions tested on:

3.13

Operating systems tested on:

Linux

Beginnen Sie mit der Überprüfung des CPython pull request 114900 und issue 113462; verfolgen Sie anschließend, wie der Attribut-Cache nach wiederholten Änderungen an Klassen deaktiviert wird. Verwenden Sie die im issue beschriebenen Fälle von ERP5 und Odoo als Performanzszenarien. Als erledigt gilt die Aufgabe, wenn die gemeldete Regression vermieden wird und zugleich das Crash-Szenario aus issue 113462 behoben wird.