Merge pull request #8149 from pytest-dev/release-6.2.1
Prepare release 6.2.1 (cherry picked from commit a566eb9c7085d7732127420bd7ce5ec1f7319fba)
This commit is contained in:
parent
9ccbf5b899
commit
56600414df
|
@ -1,2 +0,0 @@
|
||||||
Fixed bug where ``ImportPathMismatchError`` would be raised for files compiled in
|
|
||||||
the host and loaded later from an UNC mounted path (Windows).
|
|
|
@ -1,10 +0,0 @@
|
||||||
Fixed regression in ``approx``: in 6.2.0 ``approx`` no longer raises
|
|
||||||
``TypeError`` when dealing with non-numeric types, falling back to normal comparison.
|
|
||||||
Before 6.2.0, array types like tf.DeviceArray fell through to the scalar case,
|
|
||||||
and happened to compare correctly to a scalar if they had only one element.
|
|
||||||
After 6.2.0, these types began failing, because they inherited neither from
|
|
||||||
standard Python number hierarchy nor from ``numpy.ndarray``.
|
|
||||||
|
|
||||||
``approx`` now converts arguments to ``numpy.ndarray`` if they expose the array
|
|
||||||
protocol and are not scalars. This treats array-like objects like numpy arrays,
|
|
||||||
regardless of size.
|
|
|
@ -6,6 +6,7 @@ Release announcements
|
||||||
:maxdepth: 2
|
:maxdepth: 2
|
||||||
|
|
||||||
|
|
||||||
|
release-6.2.1
|
||||||
release-6.2.0
|
release-6.2.0
|
||||||
release-6.1.2
|
release-6.1.2
|
||||||
release-6.1.1
|
release-6.1.1
|
||||||
|
|
|
@ -0,0 +1,20 @@
|
||||||
|
pytest-6.2.1
|
||||||
|
=======================================
|
||||||
|
|
||||||
|
pytest 6.2.1 has just been released to PyPI.
|
||||||
|
|
||||||
|
This is a bug-fix release, being a drop-in replacement. To upgrade::
|
||||||
|
|
||||||
|
pip install --upgrade pytest
|
||||||
|
|
||||||
|
The full changelog is available at https://docs.pytest.org/en/stable/changelog.html.
|
||||||
|
|
||||||
|
Thanks to all of the contributors to this release:
|
||||||
|
|
||||||
|
* Bruno Oliveira
|
||||||
|
* Jakob van Santen
|
||||||
|
* Ran Benita
|
||||||
|
|
||||||
|
|
||||||
|
Happy testing,
|
||||||
|
The pytest Development Team
|
|
@ -28,6 +28,28 @@ with advance notice in the **Deprecations** section of releases.
|
||||||
|
|
||||||
.. towncrier release notes start
|
.. towncrier release notes start
|
||||||
|
|
||||||
|
pytest 6.2.1 (2020-12-15)
|
||||||
|
=========================
|
||||||
|
|
||||||
|
Bug Fixes
|
||||||
|
---------
|
||||||
|
|
||||||
|
- `#7678 <https://github.com/pytest-dev/pytest/issues/7678>`_: Fixed bug where ``ImportPathMismatchError`` would be raised for files compiled in
|
||||||
|
the host and loaded later from an UNC mounted path (Windows).
|
||||||
|
|
||||||
|
|
||||||
|
- `#8132 <https://github.com/pytest-dev/pytest/issues/8132>`_: Fixed regression in ``approx``: in 6.2.0 ``approx`` no longer raises
|
||||||
|
``TypeError`` when dealing with non-numeric types, falling back to normal comparison.
|
||||||
|
Before 6.2.0, array types like tf.DeviceArray fell through to the scalar case,
|
||||||
|
and happened to compare correctly to a scalar if they had only one element.
|
||||||
|
After 6.2.0, these types began failing, because they inherited neither from
|
||||||
|
standard Python number hierarchy nor from ``numpy.ndarray``.
|
||||||
|
|
||||||
|
``approx`` now converts arguments to ``numpy.ndarray`` if they expose the array
|
||||||
|
protocol and are not scalars. This treats array-like objects like numpy arrays,
|
||||||
|
regardless of size.
|
||||||
|
|
||||||
|
|
||||||
pytest 6.2.0 (2020-12-12)
|
pytest 6.2.0 (2020-12-12)
|
||||||
=========================
|
=========================
|
||||||
|
|
||||||
|
|
|
@ -28,7 +28,7 @@ Install ``pytest``
|
||||||
.. code-block:: bash
|
.. code-block:: bash
|
||||||
|
|
||||||
$ pytest --version
|
$ pytest --version
|
||||||
pytest 6.2.0
|
pytest 6.2.1
|
||||||
|
|
||||||
.. _`simpletest`:
|
.. _`simpletest`:
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue