-  update to 3.6.2
- add python-mock to buildrequires
- fix test command
- add python_mock.patch to use stdlib mock library on py3

- Update to version 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
      <https://docs.pytest.org/en/latest/mark.html#marker-revamp-and-iteration>`_,
      or jump over to details about `updating existing code to use the new APIs
      <https://docs.pytest.org/en/latest/mark.html#updating-code>`_. (`#3317
      <https://github.com/pytest-dev/pytest/issues/3317>`_)
    * 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. (`#2334
      <https://github.com/pytest-dev/pytest/issues/2334>`_)
    * Support for Python 3.7's builtin ``breakpoint()`` method, see `Using the
      builtin breakpoint function
      <https://docs.pytest.org/en/latest/usage.html#breakpoint-builtin>`_ for
      details. (`#3180 <https://github.com/pytest-dev/pytest/issues/3180>`_)
    * ``monkeypatch`` now supports a ``context()`` function which acts as a context
      manager which undoes all patching done within the ``with`` block. (`#3290
      <https://github.com/pytest-dev/pytest/issues/3290>`_)
    * 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. (`#3299

• Files Changed
• Browse Source