Auto decode content

Currently thinking of a feature, which allows you to automatically get the content of request decoded, for example in a seperate field.

now:

``` python
>>> import requests, json
>>> r = requests.get('http://search.twitter.com/search.json?q=from%3Apetermanser&rpp=1')
>>> json.loads(r.content)
{u'next_page': u'?page=2&max_id=110411755330600960&q=from%3Apetermanser&rpp=1', u'completed_in': 0.045999999999999999, u'max_id_str': u'110411755330600960', u'since_id_str': u'0', u'refresh_url': u'?since_id=110411755330600960&q=from%3Apetermanser', u'results': [{u'iso_language_code': u'en', u'from_user_id_str': u'23642932', u'text': u'@mitsuhiko you have to get a time machine.. ;)', u'created_at': u'Sun, 04 Sep 2011 17:59:48 +0000', u'profile_image_url': u'http://a3.twimg.com/profile_images/1285795312/peter.manser_normal.jpg', u'to_user_id_str': u'3260011', u'to_user': u'mitsuhiko', u'source': u'&lt;a href=&quot;http://tapbots.com/tweetbot&quot; rel=&quot;nofollow&quot;&gt;Tweetbot for iPhone&lt;/a&gt;', u'id_str': u'110411755330600960', u'from_user': u'petermanser', u'from_user_id': 23642932, u'to_user_id': 3260011, u'geo': None, u'id': 110411755330600960, u'metadata': {u'result_type': u'recent'}}], u'since_id': 0, u'results_per_page': 1, u'query': u'from%3Apetermanser', u'max_id': 110411755330600960, u'page': 1}
```

with decode feature:

``` python
>>> import requests, json
>>> r = requests.get('http://search.twitter.com/search.json?q=from%3Apetermanser&rpp=1', decode='json')
>>> r.content_decoded
{u'next_page': u'?page=2&max_id=110411755330600960&q=from%3Apetermanser&rpp=1', u'completed_in': 0.045999999999999999, u'max_id_str': u'110411755330600960', u'since_id_str': u'0', u'refresh_url': u'?since_id=110411755330600960&q=from%3Apetermanser', u'results': [{u'iso_language_code': u'en', u'from_user_id_str': u'23642932', u'text': u'@mitsuhiko you have to get a time machine.. ;)', u'created_at': u'Sun, 04 Sep 2011 17:59:48 +0000', u'profile_image_url': u'http://a3.twimg.com/profile_images/1285795312/peter.manser_normal.jpg', u'to_user_id_str': u'3260011', u'to_user': u'mitsuhiko', u'source': u'&lt;a href=&quot;http://tapbots.com/tweetbot&quot; rel=&quot;nofollow&quot;&gt;Tweetbot for iPhone&lt;/a&gt;', u'id_str': u'110411755330600960', u'from_user': u'petermanser', u'from_user_id': 23642932, u'to_user_id': 3260011, u'geo': None, u'id': 110411755330600960, u'metadata': {u'result_type': u'recent'}}], u'since_id': 0, u'results_per_page': 1, u'query': u'from%3Apetermanser', u'max_id': 110411755330600960, u'page': 1}
```

wdyt? good idea?

---
### List of possible encodings
- json
- gzip
- xml


Sorry for the delayed response.

I've been thinking about this for a while. I'm torn.

Let's build a list of possible decoders first. If there's a nice list that can be handled by the standard library, this will definitely be a good idea.


Cool :)

You mean a list of decoders to implement?

There are [a lot of mime_types](http://en.wikipedia.org/wiki/Mime_type), but I'd love to see the most important ones, such as `application/json` or `text/xml` for the beginning.


I mean a list of decoders that could easily be handled by the standard library.


Okay. I added xml.


Out of scope.