testing that the (decorated) view is not callable before taking the klass parameter
added Tests to a Class based Service with cors enabled
Merge pull request #181 from elishowk/fix-callable-decorated-view

testing that the (decorated) view is not callable before taking the klass param
pep8 setup.py & add mock as a test-dep
Add a way to opt-out of the exception handling.
Add a FAQ with a section about exception handling
General exception views shouldn't need permission.

So let's set "permission=pyramid.security.NO_PERMISSION_REQUIRED" on them!
This should fix #182.
Update the CHANGES.txt file
Bump version
Added venusion depth support to cornice.resource

This allows you more versatility in how you decorate your services with
the resource class. One particular use case is when you want to
dynamically build your resource parameters, you need to decorate the
resource decorator in order to generate the parameters. Basically, you
are introspecting the routing information from the service itself.

    # Something like this:
    @resource(
        path= '/user/{id}',
        collection_path='/user',
        accept=['text/xml', 'text/json'])
    class User(BaseService):

    # becomes something like this:
    def myresource(service_class):
        # inject the depth parameter into the parameters to offset
        # venusian's expected scope
        params = dict(service_class.get_route_params(), depth=2)
        return resource(**params)(service_class)

    @myservice
    class User(BaseService):

Implementation is similar to how cornice.service handles venusion
support.  This is needed because cornice uses the venusian module to
delegate decoration, and venusion makes assumptions about your code for
decoration eligibility. That assumption can be described as:

    “The target of decoration must be defined in the same scope that the
decoration is applied in order for the decoration to be eligible for
application.”

Venusian introspects the module from which the decorated entity is
defined.  If the the decorated entity was defined in a module other than
the module that decorator was applied, it assumes that the entity was
imported into that module and should not be decorated.

Venusion supports a decorator depth offset, which allows you to adjust
the scope of where venusion believes the decoration was applied at.
This change provides support for passing the depth parameter through the
cornice.resource decorator to venusion.
Merge pull request #187 from sbbowers/master

Added venusion depth support to cornice.resource
Add slightly more expressive error. 

It isn't documented thoroughly that Cornice only deals with JSON requests.

Actually, it could quite simply support standard www-form, with the flattened convention from Colander, couldn't it ?

Anyway, I was debugging and it took a while to figure out it was
trying to decode my www-form into JSON.  This makes it a little more explicit.
Merge pull request #188 from abourget/patch-1

Add slightly more expressive error.
fix the documentation
Add test to exemplify "collection_service_name" route use.
Add Colander validation for input other than JSON

 * add built-in support for www-form-urlencoded data (ie.
   traditional HTML form submission)
 * allow specifying custom deserializers for other input types through
   app configuration or view configuration

Includes work by Alexandre Bourget aka @abourget
Merge pull request #192 from makinacorpus/request-data-extractors

Request data extractors to allow posting other formats than JSON
Ref #195 : Add support for the traverse argument

Allows to provide a traverse argument to our Service, that will be used
by cornice for route declaration :

foo_service = cornice.Service(
        name="foo",
        path="/foo/{id}",
        traverse="/bar/baz/{id}")
Ref #195 : Add some docs

Here we document the traverse argument :
* In the Service class' docstring
* In the docs about routing
Merge pull request #196 from tonthon/master

Ref #195 : Add support for the traverse argument