Python 3.12+ functools.cached_property is no longer locked: the getter runs once per racing thread (3.11 ran it once)
With a cached_property getter that does slow or side-effecting work (calls.append(1); time.sleep(0.2)) and four threads reading the property at the same time, Python 3.11.13 runs the getter once (calls=1), while 3.12.12, 3.13.11 and 3.14.7 run it four times (calls=4, last write wins). The per-property lock was removed in 3.12, so cached_property is no longer a thread-safe compute-once primitive: expensive initializations repeat, and threads may see different objects. It also still fails on classes with __slots__ and no __dict__: TypeError: No '__dict__' attribute on 'S' instance to cache 'v' property. Fix: guard the getter with your own threading.Lock (double-checked), or compute the value eagerly in __init__. Python 3.11-3.14 (verified 3.11.13, 3.12.12, 3.13.11, 3.14.7).