Log Message:
py-test: updated to 3.6.0

Pytest 3.6.0
Features
Revamp the internals of the pytest.mark implementation with correct per node \ 
handling which fixes a number of long standing bugs caused by the old design. \ 
This introduces new Node.iter_markers(name) and Node.get_closest_mark(name) \ 
APIs. Users are strongly encouraged to read the reasons for the revamp in the \ 
docs, or jump over to details about updating existing code to use the new APIs.
Now when @pytest.fixture is applied more than once to the same function a \ 
ValueError is raised. This buggy behavior would cause surprising problems and if \ 
was working for a test suite it was mostly by accident.
Support for Python 3.7’s builtin breakpoint() method, see Using the builtin \ 
breakpoint function for details.
monkeypatch now supports a context() function which acts as a context manager \ 
which undoes all patching done within the with block.
The --pdb option now causes KeyboardInterrupt to enter the debugger, instead of \ 
stopping the test session. On python 2.7, hitting CTRL+C again exits the \ 
debugger. On python 3.2 and higher, use CTRL+D.
pytest not longer changes the log level of the root logger when the log-level \ 
parameter has greater numeric value than that of the level of the root logger, \ 
which makes it play better with custom logging configuration in user code.

Bug Fixes
A rare race-condition which might result in corrupted .pyc files on Windows has \ 
been hopefully solved.
Also use iter_marker for discovering the marks applying for marker expressions \ 
from the cli to avoid the bad data from the legacy mark storage.
When showing diffs of failed assertions where the contents contain only \ 
whitespace, escape them using repr() first to make it easy to spot the \ 
differences.