#18659: Remove `request.REQUEST`
------------------------------------------------+------------------------
Reporter: aaugustin | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (Other) | Version: 1.4
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
`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`.
--
Ticket URL: <https://code.djangoproject.com/ticket/18659>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
