Changes between Initial Version and Version 1 of Ticket #26668


Ignore:
Timestamp:
05/26/2016 04:42:02 AM (4 years ago)
Author:
Will Pimblett
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #26668 – Description

    initial v1  
    2323}}}
    2424
    25 Workaround is to replace `response.content` with `unicode(response.content, encoding=settings.DEFAULT_ENCODING)`. 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.
     25Workaround 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.
    2626
    2727I'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.
Back to Top