id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
30278	Using del on uncalled cached_property throws exception.	Matthew Schinckel	nobody	"It's explicitly documented that you may use `del` (or `delattr`) to force a cached_property to recalculate the next time it's called.

However, if you try to `del` a cached_property that has never been evaluated, then an AttributeError is raised.

There doesn't seem to be a way to detect if a cached_property has been evaluated or not, as `hasattr(foo, 'bar')` results in the evaluation of the cached_property.

It's entirely possible that this is something that is beyond the capability of the way cached_property is implemented, but it still feels wrong to me.

(Likewise, if you attempt to `del foo.bar` twice without evaluation in between, you will raise an AttributeError)."	Bug	closed	Utilities	dev	Normal	invalid	cached_property		Unreviewed	0	0	0	0	0	0