Preparing release version 5.3.4 (#6516)
Preparing release version 5.3.4
This commit is contained in:
		
						commit
						ddfa41b5a7
					
				| 
						 | 
				
			
			@ -1,2 +0,0 @@
 | 
			
		|||
Revert `#6436 <https://github.com/pytest-dev/pytest/issues/6436>`__: unfortunately this change has caused a number of regressions in many suites,
 | 
			
		||||
so the team decided to revert this change and make a new release while we continue to look for a solution.
 | 
			
		||||
| 
						 | 
				
			
			@ -6,6 +6,7 @@ Release announcements
 | 
			
		|||
   :maxdepth: 2
 | 
			
		||||
 | 
			
		||||
 | 
			
		||||
   release-5.3.4
 | 
			
		||||
   release-5.3.3
 | 
			
		||||
   release-5.3.2
 | 
			
		||||
   release-5.3.1
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
| 
						 | 
				
			
			@ -0,0 +1,20 @@
 | 
			
		|||
pytest-5.3.4
 | 
			
		||||
=======================================
 | 
			
		||||
 | 
			
		||||
pytest 5.3.4 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/latest/changelog.html.
 | 
			
		||||
 | 
			
		||||
Thanks to all who contributed to this release, among them:
 | 
			
		||||
 | 
			
		||||
* Bruno Oliveira
 | 
			
		||||
* Daniel Hahler
 | 
			
		||||
* Ran Benita
 | 
			
		||||
 | 
			
		||||
 | 
			
		||||
Happy testing,
 | 
			
		||||
The pytest Development Team
 | 
			
		||||
| 
						 | 
				
			
			@ -28,6 +28,16 @@ with advance notice in the **Deprecations** section of releases.
 | 
			
		|||
 | 
			
		||||
.. towncrier release notes start
 | 
			
		||||
 | 
			
		||||
pytest 5.3.4 (2020-01-20)
 | 
			
		||||
=========================
 | 
			
		||||
 | 
			
		||||
Bug Fixes
 | 
			
		||||
---------
 | 
			
		||||
 | 
			
		||||
- `#6496 <https://github.com/pytest-dev/pytest/issues/6496>`_: Revert `#6436 <https://github.com/pytest-dev/pytest/issues/6436>`__: unfortunately this change has caused a number of regressions in many suites,
 | 
			
		||||
  so the team decided to revert this change and make a new release while we continue to look for a solution.
 | 
			
		||||
 | 
			
		||||
 | 
			
		||||
pytest 5.3.3 (2020-01-16)
 | 
			
		||||
=========================
 | 
			
		||||
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
| 
						 | 
				
			
			@ -475,10 +475,10 @@ Running it results in some skips if we don't have all the python interpreters in
 | 
			
		|||
.. code-block:: pytest
 | 
			
		||||
 | 
			
		||||
   . $ pytest -rs -q multipython.py
 | 
			
		||||
   ssssssssssssssssssssssss...                                          [100%]
 | 
			
		||||
   ssssssssssss...ssssssssssss                                          [100%]
 | 
			
		||||
   ========================= short test summary info ==========================
 | 
			
		||||
   SKIPPED [12] $REGENDOC_TMPDIR/CWD/multipython.py:29: 'python3.5' not found
 | 
			
		||||
   SKIPPED [12] $REGENDOC_TMPDIR/CWD/multipython.py:29: 'python3.6' not found
 | 
			
		||||
   SKIPPED [12] $REGENDOC_TMPDIR/CWD/multipython.py:29: 'python3.7' not found
 | 
			
		||||
   3 passed, 24 skipped in 0.12s
 | 
			
		||||
 | 
			
		||||
Indirect parametrization of optional implementations/imports
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
| 
						 | 
				
			
			@ -436,7 +436,7 @@ Here is a nice run of several failures and how ``pytest`` presents things:
 | 
			
		|||
            items = [1, 2, 3]
 | 
			
		||||
            print("items is {!r}".format(items))
 | 
			
		||||
    >       a, b = items.pop()
 | 
			
		||||
    E       TypeError: cannot unpack non-iterable int object
 | 
			
		||||
    E       TypeError: 'int' object is not iterable
 | 
			
		||||
 | 
			
		||||
    failure_demo.py:181: TypeError
 | 
			
		||||
    --------------------------- Captured stdout call ---------------------------
 | 
			
		||||
| 
						 | 
				
			
			@ -516,7 +516,7 @@ Here is a nice run of several failures and how ``pytest`` presents things:
 | 
			
		|||
        def test_z2_type_error(self):
 | 
			
		||||
            items = 3
 | 
			
		||||
    >       a, b = items
 | 
			
		||||
    E       TypeError: cannot unpack non-iterable int object
 | 
			
		||||
    E       TypeError: 'int' object is not iterable
 | 
			
		||||
 | 
			
		||||
    failure_demo.py:222: TypeError
 | 
			
		||||
    ______________________ TestMoreErrors.test_startswith ______________________
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
| 
						 | 
				
			
			@ -442,7 +442,7 @@ Now we can profile which test functions execute the slowest:
 | 
			
		|||
 | 
			
		||||
    ========================= slowest 3 test durations =========================
 | 
			
		||||
    0.30s call     test_some_are_slow.py::test_funcslow2
 | 
			
		||||
    0.21s call     test_some_are_slow.py::test_funcslow1
 | 
			
		||||
    0.20s call     test_some_are_slow.py::test_funcslow1
 | 
			
		||||
    0.11s call     test_some_are_slow.py::test_funcfast
 | 
			
		||||
    ============================ 3 passed in 0.12s =============================
 | 
			
		||||
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
| 
						 | 
				
			
			@ -28,7 +28,7 @@ Install ``pytest``
 | 
			
		|||
.. code-block:: bash
 | 
			
		||||
 | 
			
		||||
    $ pytest --version
 | 
			
		||||
    This is pytest version 5.x.y, imported from $PYTHON_PREFIX/lib/python3.7/site-packages/pytest/__init__.py
 | 
			
		||||
    This is pytest version 5.x.y, imported from $PYTHON_PREFIX/lib/python3.6/site-packages/pytest/__init__.py
 | 
			
		||||
 | 
			
		||||
.. _`simpletest`:
 | 
			
		||||
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Loading…
	
		Reference in New Issue