Yes, although it is not the so much the variable name that causes this, not directly.
When Python exits, all modules are deleted too. The way modules are cleaned up is by setting all globals in a module to None (so those references no longer refer to the original objects). Those globals are keys in a dictionary object, and as dictionaries are ordered arbitrarily, renaming one variable can change the order in which variables are cleared.
When you renamed v to vb, you altered the order in which variables are cleared, and now Person is cleared last.
One work-around is to use type(self).num_of_people -= 1 in the __del__ method instead:
def __del__(self):
type(self).num_of_people -= 1
because the instance will always have a reference to the class still, or test if Person is not set to None:
def __del__(self):
if Person is not None:
Person.num_of_people -= 1
Two notes:
CPython 3.4 no longer sets globals to None (in most cases), as per Safe Object Finalization; see PEP 442.
CPython 3.3 automatically applies a randomized hash salt to the str keys used in a globals dictionary; this makes the behaviour you observed even more random, merely re-running your code several times may or may not trigger the error message.
