I'm running into this, too, on Python 3.9.2; in my case it's causing segmentation faults in a wxPython-based application. 

Those segfaults aren't the fault of the reference cycle, of course; they're a result of wxPython being finicky about object cleanup order, but the existence of the enum reference cycle does make it harder to maneuver wxPython into a place where it doesn't crash.