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
18659	Remove `request.REQUEST`	Aymeric Augustin	Bouke Haarsma	"`request.REQUEST` provides indifferent access to `request.GET` or `request.POST` (PHP style).

This attribute is a legacy from the pre-1.0 days, when you could access the `GET` or `POST` data using dict syntax on the request object. `request.REQUEST` was introduced in 1.0 to make this operation more explicit, with an easy upgrade path.

It's hardly ever a good design pattern to handle `GET` and `POST` identically, and it's our responsibility not to provide tools who are more likely to result in bad code than anything else. So I think it's time to deprecate this attribute.

We could deprecate `django.utils.datastructures.MergeDict` at the same time — it's a 100-lines long class whose sole purpose is to support `request.REQUEST`.

"	Cleanup/optimization	closed	HTTP handling	dev	Normal	fixed		marc.tamlyn@… eduardocereto@… bmispelon@…	Accepted	1	0	0	1	0	0