WIP: alternate mode for repeating response handlers #256
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an alternate version of pull #254, with the difference
in gabbi/suitemaker.py where response_handlers is only extended
if the response_* key has not been seen before. This means that
if the YAMLDiskLoadingJSONHandler is turned on it does all the
work of the JSONHandler for respone handling, because it is only
present once.
At the same time, the existing handing for content handlers means
that custom handlers which accept a content-type are used first (and
only) for the content type it accepts.
The issues with pytest and files having the same name remain
here. I tried to make some change to pytest test loading to
make the global cache use more distinguishing keys, but it was
distracting from progressing on the other work, so I'll deal with
that separately.