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
34973	Allow making unpickling warnings an error	stefan6419846	nobody	"In #21430 (https://github.com/django/django/commit/42736ac), unpickling has been changed to log a warning for incompatible versions. While this raises awareness, this is not really practical if you have lots of deployments to consider.

We are using mostly automated deployments to quickly provide the latest changes to our customers. Whenever we update to a newer Django, we need to clear the whole cache. Automating this requires special handling, as running the cache invalidation on every deployment seems to be overkill for unrelated updates - thus some custom logic is required to only force an invalidation on Django package changes when necessary at the moment.

For this reason, I would like to propose an additional/changed solution which turns this into hard failures which can be handled by my application without having to invalidate the cache itself. This way, I am able to cleanly detect this and handle it appropriately.

Due to being a backwards-incompatible change, this might be changed by a new setting which defaults to the old behavior."	New feature	closed	Database layer (models, ORM)	4.2	Normal	wontfix			Unreviewed	0	0	0	0	0	0