* Drop support for legacy Python 2.7
* Upgrade Python syntax with pyupgrade --py3-plus
* Trim testing matrix to remove python2
* re-enable python3.8 in travis as tests that are not allowed to fail
* Remove some six
* The future is now
* Remove Python 2 imports
* Add back example, but change py27 to py36
* Remove redundant compat.py
* Blacken
* Credit hugovk in changelog
WIP Updating Sphinx Docs and AutoDoc
* Fix AutoDoc and update Sphinx theme to python_doc_theme
* Fix#420, autodoc even undocumented (docstring-less) method signatures
* Doc theme 'nature'. Add global TOC to doc sidebar
* Comment last reference to package six
* Changelog is now a consistent format
* Yet another documentation fix for links and title hierarchy
* Start work on new SVG logo
test SVG in README
trying to test new SVG logo in README
Apply centering
Apply readme logo centering
Trying to align image
Trying random shit
trying align right
add emoji
Large logo has higher priority
Change title hierarchy
Actually use a H1
Try again
try and organise badges
revert link back to point at master
* updated new take on VCR logo as SVG code
* Testing modern logo in docs
* Add sanitize for rendering SVG
* Switch to alabaster theme
* Update vcrpy logo (#503)
* Add credit for V4 logo changes.
* Add rewind and play animation
* Add svg into ReadTheDocs static assets so that it can be hosted so the animations work.
* Need to embedd the SVG for ReadTheDocs somewhere so I can get the link to later embed in the README
Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
Co-authored-by: Sean Bailey <sean@seanbailey.io>
Format with line length 110 to match flake8
make black part of linting check
Update travis spec for updated black requirements
Add diff output for black on failure
update changelog
In order to use the new assert mechanism that returns explicit assertion failure message, all the default matchers does not return a boolean, but only do an assert statement with a basic assertion message (value_1 != value_2).
The requests_match function has been refactored to use the 'get_matchers_results' function in order to have explicit failures that are logged if any.
Many unit tests have been changed as the matchers does not return a boolean value anymore.
Note: Only the matchers "body" and "raw_body" does not have an assertion message, the body values might be big and not useful to be display to spot the differences.
The function returns two list:
- the first one is the list of matchers names that have succeeded.
- the second is a list of tuples with the failed matchers names and the related assertion message like this ("matcher_name", "assertion_message").
If the second list is empty, it means that all the matchers have passed.
A matcher can now return other results than a boolean :
- An AssertionError exception meaning that the matcher failed, with the exception we get the assertion failure message.
- None, in case we do an assert in the matcher, meaning that the assertion has passed, the matcher is considered as a success then.
- Boolean that indicates if a matcher failed or not. If there is no match, a boolean does not give any clue what it is the differences compared to the assertion.
