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
29079	Django settings should not cache user wrapped settings	Riccardo Di Virgilio	nobody	"django 2.0 and 1.11 are breaking my custom settings.

I'm using settings.configure with a custom object that can change his properties if the environment is changing.
Starting from 1.11 the function {{{ LazySettings.__getattr__}}} is caching the values that are returned from the custom object that is provided by the user.

If all the custom object can do is to provide static values why I should use a custom object at all instead of a regular module? 

In my view is an user needs to use a custom object as settings is because he needs advanced features that cannot be archived by a normal module. 
It's very easy to add cache to all properties in a custom object if this is behavior the user needs, but is really hard to disable this (if not impossibile for the way this code is written).

If the staff is strongly against disabling the cache by default, can we at least add an option to disable it?

thanks."	Bug	closed	Core (Other)	1.11	Normal	wontfix		Adam Johnson	Unreviewed	0	0	0	0	0	0