#23006: test.Client: provide os.environ with request.meta for consistency
-----------------------------------+--------------------
Reporter: blueyed | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------
When using the test.Client the information from os.environ is not present
in request.META, although it will be there usually (runser/uwsgi/...).
This causes e.g. the `debug.technical_500_response` to look different when
accessed via the test client.
This is important for (advanced) testing, when you want to see if e.g.
`settings.SECRET_KEY` would end up in the rendered content: with the test
client it will currently never be there, although you have
`DJANGO_SECRECT_KEY` in the environment and this would show up when not
using the test client (via rendering of request.META).
(I have mentioned this in
[https://code.djangoproject.com/ticket/23004#comment:2 a comment to
another issue], and since I appear to not miss something obvious, I am
creating a new issue for it.)
--
Ticket URL: <https://code.djangoproject.com/ticket/23006>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/050.87b0415cf8aa9a9a2ccca429460459cb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
