understatement with that. Saw someone trying to avoid using a metaclass for that, "had" to use descriptor objects which all used the same global counter to work out their order
GvR called it "The Killing Joke" for a reason.
This is a clear case of "negative productivity": People are working "harder than a cat trying to bury a turd on a marble floor" to pee in my soup. It makes me grumpy.
multiple global values to track state, since can't bind the state to the class' creation, since the conversion to the final form of the class happened after its creation, vs being able to bind the state to the class' creation, since the conversion happens as the class is created
(I'm joking, but only barely.)
The customer requests the following
@?
class somename (?):
an_attr_a = ADescriptor(somestuff)
an_attr_1 = ADescriptor(somestuff)
an_attr_a1 = ADescriptor(somestuff)