Preparing release version 3.6.0

This commit is contained in:
Bruno Oliveira
2018-05-23 00:07:48 +00:00
parent c55db1faac
commit d70e910b65
18 changed files with 129 additions and 28 deletions
-1
View File
@@ -1 +0,0 @@
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.
-1
View File
@@ -1 +0,0 @@
A rare race-condition which might result in corrupted ``.pyc`` files on Windows has been hopefully solved.
-1
View File
@@ -1 +0,0 @@
``pytest`` now depends on the `python-atomicwrites <https://github.com/untitaker/python-atomicwrites>`_ library.
-1
View File
@@ -1 +0,0 @@
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.
-2
View File
@@ -1,2 +0,0 @@
``monkeypatch`` now supports a ``context()`` function which acts as a context manager which undoes all patching done
within the ``with`` block.
-2
View File
@@ -1,2 +0,0 @@
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.
-1
View File
@@ -1 +0,0 @@
Change documentation copyright year to a range which auto-updates itself each time it is published.
-3
View File
@@ -1,3 +0,0 @@
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.
-4
View File
@@ -1,4 +0,0 @@
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>`_.
-1
View File
@@ -1 +0,0 @@
Update all pypi.python.org URLs to pypi.org.
-1
View File
@@ -1 +0,0 @@
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.
-1
View File
@@ -1 +0,0 @@
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.
-3
View File
@@ -1,3 +0,0 @@
Detect `pytest_` prefixed hooks using the internal plugin
manager since ``pluggy`` is deprecating the ``implprefix``
argument to ``PluginManager``.
-5
View File
@@ -1,5 +0,0 @@
Import ``Mapping`` and ``Sequence`` from ``_pytest.compat`` instead of directly
from ``collections`` in ``python_api.py::approx``. Add ``Mapping`` to
``_pytest.compat``, import it from ``collections`` on python 2, but from
``collections.abc`` on Python 3 to avoid a ``DeprecationWarning`` on
Python 3.7 or newer.