Add check for 'resource_name' Meta class attribute before building the key from the class name. This allows for doc URLs that match the api URLs when 'resource_name' is specified. This reduces confusion when trying to locate the documentation for an api resource that has in fact specified 'resource_name'.
Remove extranneous whitespace.
Create SmartTag model to demonstrate multi-word resource names.
Create corresponding SmartTag resource with explicitly defined 'resource_name' attribute that will be used for its TastyFactory key.
Write unit test to check that the key of a resource instance created by TastyFactory can utilize the 'resource_name' meta attribute if present.
Merge pull request #11 from thagat/feature/pip_dependencies

Setup.py now handles pip dependencies
Merge upstream changes.
Merge pull request #6 from jondbaker/master

Use 'resource_name' for key if available.
Merge branch 'master' of https://github.com/juanique/django-chocolate into feature/colliding_model_names

Conflicts:
	test_project/blog/tests.py