Opened 8 years ago

Closed 8 years ago

#26668 closed Bug (invalid)

HTTPResponse.content is not unicode in context of test cases.

Reported by: Will Pimblett Owned by: nobody
Component: HTTP handling Version: 1.8
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Will Pimblett)

Came across the following when adding from __future__ import unicode_literals to my

When doing the following for an existing view with an expected output:

def test_page_not_found(self):
        url = '/help/404/'
        c = self.get_client()
        response = c.get(url)
        self.assertIn("Page Not Found", response.content)

We get:

ERROR: test_page_not_found (xsd_help.tests.HelpViewTest)
Traceback (most recent call last):
  File "/builds/wjdp/xsacdb/src/xsd_help/", line 23, in test_page_not_found
    self.assertTrue("Page Not Found" in response.content)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 21370: ordinal not in range(128)

Workaround is to replace response.content with unicode(response.content, encoding=settings.DEFAULT_CHARSET). According to what I could find in the docs the content should be encoded with uft-8, I think this issue is because request.content is a bytestring without an encoding attached.

I'm raising this either in case this in not expected or if it is suggesting a more descriptive error is generated and/or better documentation for those who come across this - there was a *lot* of headscratching needed to find the root of these test failures.

Another suggestion: could we have another property of HTTPResponse that gives us a unicode string rather than a bytestring for test cases?

See for another similar use case.

Change History (6)

comment:1 by Will Pimblett, 8 years ago

Description: modified (diff)

comment:2 by Simon Charette, 8 years ago

The SimpleTestCase class already provides the assertContains method for this use case.

I'm afraid there's not much we can do to make the error message more descriptive as that's standard Python stuff.

comment:3 by Simon Charette, 8 years ago

I also noticed that the Porting to Python 3 guide mentions why assertContains should be used instead.

Is this the reason you added the from __future__ import unicode_literals import in the first place?

comment:4 by Will Pimblett, 8 years ago

Ah, must have glossed over that, assertContains seems to fix all of this. unicode_literals was unrelated I think, just fixing up use of literals.

comment:5 by Will Pimblett, 8 years ago

Feel free to mark as invalid.

comment:6 by Simon Charette, 8 years ago

Resolution: invalid
Status: newclosed
Note: See TracTickets for help on using tickets.
Back to Top