Django 5.1 Added query_params Argument

Good news! Django 5.1 has already addressed this exact issue by introducing a query_params parameter to all Client HTTP methods, including post(), get(), put(), delete(), etc.

New query_params Parameter

The query_params parameter works exactly as you described - it allows you to set query string parameters separately from the request body data. This makes the API more consistent with popular HTTP libraries like requests and httpx.

Here's an example of using it with post():

PYTHONCopied
>>> c = Client()
>>> c.post(
...     "/login/", 
...     {"name": "fred", "passwd": "secret"}, 
...     query_params={"visitor": "true"}
... )

In this example:

• {"name": "fred", "passwd": "secret"} is sent as POST data in the request body
• visitor=true is added to the query string in the URL

Benefits of the New Parameter

1. Consistency across methods: All HTTP methods now handle query parameters in the same way
2. Clearer separation of concerns: Query parameters and request body data are now clearly separated
3. Better API design: Matches the pattern used by popular HTTP libraries
4. Works with all HTTP methods: Even methods like post(), put(), etc. that already use data for the request body

This change was introduced in Django 5.1, as noted in the "Changed in Django 5.1" note at the end of each method's documentation.