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
21200	"Inconsistent handling of ""PickleError"" between cache backends"	t.chaumeny@…	Florian Apolloner <florian@…>	"It looks like a `PickleError` raised while caching some object will get caught when using `LocMemCache` (see https://github.com/django/django/blob/728548e483a5a3486939b0c8e62520296587482e/django/core/cache/backends/locmem.py#L30) whilst it won't when using `DatabaseCache` (for instance, see https://github.com/django/django/blob/728548e483a5a3486939b0c8e62520296587482e/django/core/cache/backends/db.py#L114).

I can see no valid reason why the behavior regarding pickle errors should differ among different cache backends and this can lead to errors when tests do not use the same backend as production (it just happened to me with a pickle error : `a class that defines __slots__ without defining __getstate__ cannot be pickled`)"	Bug	closed	Core (Cache system)	dev	Normal	fixed			Accepted	1	0	0	0	0	0