* status: assigned => closed
* ui_ux: => 0
* resolution: => wontfix
* easy: => 0
Comment:
As pointed out by Russell in the mailing list thread linked above, this is
a significant increase of the scope of the test client, and it could be
considered feature creep. Parsing HTML is not as trivial a task as it
seems, even with Python's stdlib; browsers do incredible things to get it
right in almost all cases.
We're about to introduce support for live browser testing (for instance
with Selenium) in #2879 and I think it's a better path forwards.
It seems to me that the work on this ticket could live outside of trunk as
a subclass of the test client, couldn't it? It would be a good candidate
for djangosnippets.
--
Ticket URL: <https://code.djangoproject.com/ticket/11797#comment:21>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Comment (by Thomas Güttler):
Just for the records, here is an example how to parse a form from
`response.content` and submit it again with the Django TestClient:
https://stackoverflow.com/a/65603777/633961
--
Ticket URL: <https://code.djangoproject.com/ticket/11797#comment:22>