Added 'hammock' to 'docs/tools.rst'
BACKWARD-INCOMPATIBLE: Tastypie now supports much more granular authorization checks, as well as saving deeply-nested data.

This patch was over a year in the making. Thanks to Yoav Aner for the report & for security feedback, as well as all the others who reported similar issues.
Because Sphinx.
Added docs on using ``bundle.request``.
Fix for failing GIS tests.
Merge pull request #669 from kadirpekel/patch-1

Added 'hammock' to 'docs/tools.rst'
Added the ``use_in`` argument to fields so you can exclude certain fields when retriving a list
of resources vs a single resource.

* Applied patch described in https://github.com/toastdriven/django-tastypie/issues/526.
* Added the ability to make the ``use_in`` argument a callable
* Made ``use_in`` argument available to related fields
* Added the appropriate authors. Thanks to @funkybob for the original patch and @numan for the PR, enhancements, and tests.
Merge pull request #808 from georgedorn/tests/gis

Fix for failing GIS tests.
Added the ability to control full dehydration of related resources based on whether the
request is for a single resource or a list of resources.

This was done by adding 2 new keyword arguments for related fields: ``full_list``
and ``full_detail`` which accept ``True`` or ``False``. Both arguments also accept a
callable that accept a bundle, to determine if the field should be dehydrated based
on the request.
Fixes ``ApiKeyAuthentication`` security issue (#795).

``ApiKeyAuthentication`` assigns user to request object basing only on
username checks what will change current user to any provided through
username value. This caused an security vulnerability when used in conjuction
with other auth backends using ``MultiAuthentication``.

Added tests for security issue described in #795
Fixed a bug where JSON/JSONP was returning an invalid ``charset`` within the MIME type. Thanks to dstufft for the report!
BACKWARD-INCOMPATIBLE: Tastypie no longer returns plain HTML errors. This mitigates a variety of XSS-style attacks. Thanks to Philip, Semion & others who reported this!
BACKWARD-INCOMPATIBLE: JSONP is now disabled by default for greater security. Thanks to bregenspan for the report!
Updated the backward incompatible notes.
Bumped to v0.9.12!

This release features security updates that are recommended for all users of Tastypie.
Started the v0.9.13 work.
Add texinfo target to docs makefile
Changed Resource.patch_list to respect always_return data.
Correct override_urls check in Api (closes #692)

This applies the same change which #516 made to Resource to only issue
the deprecation warning when override_urls() actually returns something.

This also changes the logic in both locations to avoid calling
override_urls() more than once
Handle malformed HTTP Accept values

Some clients cause tastypie to return a 500 error because they send a request
with an HTTP Accept header which contains an invalid MIME type (e.g. any value
without a "/" other than "*", which mimeparse handles).

determine_format() now raises BadRequest any time mimeparse fails.
Resources now handle this by returning HTTP 400 immediately rather than
the normal error response