Whoops, I was using the terminology "we should use the > -r.text
method, not the r.content method. r.content" which should have been
attribute anyway
On Jan 6, 2013 4:24 AM, "sprt" notifications@github.com wrote:

In docs/user/advanced.rst:

@@ -313,17 +313,12 @@ out what type of content it is. Do this like so::
...
application/json; charset=utf-8

-So, GitHub returns JSON. That's great, we can use the JSON module to turn it
-into Python objects. Because GitHub returned UTF-8, we should use the
-r.text method, not the r.content method. r.content returns a
-bytestring, while r.text returns a Unicode-encoded string. I have no plans
-to perform byte-manipulation on this response, so I want any Unicode code
-points encoded.
+So, GitHub returns JSON. That's great, we can use the r.json method to

Typo: r.json should be r.json()

—
Reply to this email directly or view it on GitHubhttps://github.com/kennethreitz/requests/pull/1085/files#r2559427.