Raise ApiFieldError on invalid datetimes
Update docs/who_uses.rst

Added dbpatterns to who uses
Fixed 500 error on invalid order_by parameter; closes #755
BACKWARDS-INCOMPATIBLE: Format Hardening Release

Format Hardening Security Release

* XML decoding has been wrapped in the defusedxml library
* XML requests may no longer include DTDs by default
* Deserialization will return HTTP 400 for any XML decode errors
* Add `TASTYPIE_DEFAULT_FORMATS` setting to globally restrict the set of
  supported formats (closes #833)
* Content negotiation will return an error for malformed accept headers (closes #832)
* The Api class itself now allows a custom serializer (closes #817)
* The serialization documentation has been upgraded with security advice

Backwards-incompatible changes:

* XML serialization:
    - defusedxml is now required
    - defusedxml requires lxml 3 or later

    ``pip install defusedxml "lxml>=3"``
* Python 2.5 is no longer officially supported because defusedxml requires
  Python 2.6 or later.
fixed authorization if auth function returns False

* added mock to allow easier overwritting of auth
  functions
* tested when authorization *_detail function returns
  False - tests were failing. i.e. request was
  authorized, when it shouldn't have been
* updated code to raise an Unauthorized if *_detail
  functions return False
Fixed typo, should be CleanedDataFormValidation.
Added versiontools support!
Added in rose for simpler versioning.
Bumped to v0.9.13!
Removed rose. Bumped to v0.9.14!
Updated stray 0.9.13 references
Docs: add release notes section

* Added index links
* Added release notes for 0.9.13
"""``use_in`` was not being properly used for various ``list`` endpoints"""
"""enhanced tests for ``use_in``"""

Thanks to @cristiano2lopes for pointing this out, fixing the actual issue and writing some of the tests. Fixes #841.
Error handling: better logging exc_info usage

A simple True will do - the logging module just checks that exc_info is
not false.
Resource: send got_request_exception on errors

The Resource _handle_500 method will now dispatch
django.core.signals.got_request_exception during exception processing.
This makes tastypie play nicely with sentry and any other apps listening
in for exceptions.

Thanks to Andrew McCloud (@amccloud) for the patch!

NOTE: the mock library was added to the test requirements to simplify
      this and other tests.

Closes #827
If no object_class is present, do not try to instantiate an object when building the bundle. This does not affect model-based resources; however, the assumption that had been made that an object_class is always going to be present is not valid when using custom Resource objects that are not necessarily model-based.
Fixes all deprecation warnings for Django 1.5.  Thanks, shibz
Merging numerous fixes for django 1.5's custom user models, as well as backwards-compatability fixes.
Add my self to AUTHORS
Merge pull request #888 from vbabiy/authors

Add my self to AUTHORS