Preparing release version 5.2.3 (#6190)
Preparing release version 5.2.3
This commit is contained in:
		
						commit
						e856638ba0
					
				| 
						 | 
					@ -18,6 +18,22 @@ with advance notice in the **Deprecations** section of releases.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
.. towncrier release notes start
 | 
					.. towncrier release notes start
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					pytest 5.2.3 (2019-11-14)
 | 
				
			||||||
 | 
					=========================
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					Bug Fixes
 | 
				
			||||||
 | 
					---------
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					- `#5830 <https://github.com/pytest-dev/pytest/issues/5830>`_: The first test in a package (``__init__.py``) marked with ``@pytest.mark.skip`` is now correctly skipped.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					- `#6099 <https://github.com/pytest-dev/pytest/issues/6099>`_: Fix ``--trace`` when used with parametrized functions.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					- `#6183 <https://github.com/pytest-dev/pytest/issues/6183>`_: Using ``request`` as a parameter name in ``@pytest.mark.parametrize`` now produces a more
 | 
				
			||||||
 | 
					  user-friendly error.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					
 | 
				
			||||||
pytest 5.2.2 (2019-10-24)
 | 
					pytest 5.2.2 (2019-10-24)
 | 
				
			||||||
=========================
 | 
					=========================
 | 
				
			||||||
 | 
					
 | 
				
			||||||
| 
						 | 
					
 | 
				
			||||||
| 
						 | 
					@ -1 +0,0 @@
 | 
				
			||||||
Fix fail skipping the first test in package marked as ``skip``
 | 
					 | 
				
			||||||
| 
						 | 
					@ -1 +0,0 @@
 | 
				
			||||||
Fix ``--trace`` when used with parametrized functions.
 | 
					 | 
				
			||||||
| 
						 | 
					@ -1,2 +0,0 @@
 | 
				
			||||||
Using ``request`` as a parameter name in ``@pytest.mark.parametrize`` now produces a more
 | 
					 | 
				
			||||||
user-friendly error.
 | 
					 | 
				
			||||||
| 
						 | 
					@ -6,6 +6,7 @@ Release announcements
 | 
				
			||||||
   :maxdepth: 2
 | 
					   :maxdepth: 2
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					   release-5.2.3
 | 
				
			||||||
   release-5.2.2
 | 
					   release-5.2.2
 | 
				
			||||||
   release-5.2.1
 | 
					   release-5.2.1
 | 
				
			||||||
   release-5.2.0
 | 
					   release-5.2.0
 | 
				
			||||||
| 
						 | 
					
 | 
				
			||||||
| 
						 | 
					@ -0,0 +1,28 @@
 | 
				
			||||||
 | 
					pytest-5.2.3
 | 
				
			||||||
 | 
					=======================================
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					pytest 5.2.3 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:
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					* Anthony Sottile
 | 
				
			||||||
 | 
					* Brett Cannon
 | 
				
			||||||
 | 
					* Bruno Oliveira
 | 
				
			||||||
 | 
					* Daniel Hahler
 | 
				
			||||||
 | 
					* Daniil Galiev
 | 
				
			||||||
 | 
					* David Szotten
 | 
				
			||||||
 | 
					* Florian Bruhin
 | 
				
			||||||
 | 
					* Patrick Harmon
 | 
				
			||||||
 | 
					* Ran Benita
 | 
				
			||||||
 | 
					* Zac Hatfield-Dodds
 | 
				
			||||||
 | 
					* Zak Hassan
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					Happy testing,
 | 
				
			||||||
 | 
					The pytest Development Team
 | 
				
			||||||
| 
						 | 
					@ -475,10 +475,10 @@ Running it results in some skips if we don't have all the python interpreters in
 | 
				
			||||||
.. code-block:: pytest
 | 
					.. code-block:: pytest
 | 
				
			||||||
 | 
					
 | 
				
			||||||
   . $ pytest -rs -q multipython.py
 | 
					   . $ pytest -rs -q multipython.py
 | 
				
			||||||
   ssssssssssssssssssssssss...                                          [100%]
 | 
					   ssssssssssss...ssssssssssss                                          [100%]
 | 
				
			||||||
   ========================= short test summary info ==========================
 | 
					   ========================= short test summary info ==========================
 | 
				
			||||||
   SKIPPED [12] $REGENDOC_TMPDIR/CWD/multipython.py:30: 'python3.5' not found
 | 
					   SKIPPED [12] $REGENDOC_TMPDIR/CWD/multipython.py:30: 'python3.5' not found
 | 
				
			||||||
   SKIPPED [12] $REGENDOC_TMPDIR/CWD/multipython.py:30: 'python3.6' not found
 | 
					   SKIPPED [12] $REGENDOC_TMPDIR/CWD/multipython.py:30: 'python3.7' not found
 | 
				
			||||||
   3 passed, 24 skipped in 0.12s
 | 
					   3 passed, 24 skipped in 0.12s
 | 
				
			||||||
 | 
					
 | 
				
			||||||
Indirect parametrization of optional implementations/imports
 | 
					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]
 | 
					            items = [1, 2, 3]
 | 
				
			||||||
            print("items is {!r}".format(items))
 | 
					            print("items is {!r}".format(items))
 | 
				
			||||||
    >       a, b = items.pop()
 | 
					    >       a, b = items.pop()
 | 
				
			||||||
    E       TypeError: cannot unpack non-iterable int object
 | 
					    E       TypeError: 'int' object is not iterable
 | 
				
			||||||
 | 
					
 | 
				
			||||||
    failure_demo.py:181: TypeError
 | 
					    failure_demo.py:181: TypeError
 | 
				
			||||||
    --------------------------- Captured stdout call ---------------------------
 | 
					    --------------------------- 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):
 | 
					        def test_z2_type_error(self):
 | 
				
			||||||
            items = 3
 | 
					            items = 3
 | 
				
			||||||
    >       a, b = items
 | 
					    >       a, b = items
 | 
				
			||||||
    E       TypeError: cannot unpack non-iterable int object
 | 
					    E       TypeError: 'int' object is not iterable
 | 
				
			||||||
 | 
					
 | 
				
			||||||
    failure_demo.py:222: TypeError
 | 
					    failure_demo.py:222: TypeError
 | 
				
			||||||
    ______________________ TestMoreErrors.test_startswith ______________________
 | 
					    ______________________ TestMoreErrors.test_startswith ______________________
 | 
				
			||||||
| 
						 | 
					
 | 
				
			||||||
| 
						 | 
					@ -28,7 +28,7 @@ Install ``pytest``
 | 
				
			||||||
.. code-block:: bash
 | 
					.. code-block:: bash
 | 
				
			||||||
 | 
					
 | 
				
			||||||
    $ pytest --version
 | 
					    $ pytest --version
 | 
				
			||||||
    This is pytest version 5.x.y, imported from $PYTHON_PREFIX/lib/python3.7/site-packages/pytest.py
 | 
					    This is pytest version 5.x.y, imported from $PYTHON_PREFIX/lib/python3.6/site-packages/pytest.py
 | 
				
			||||||
 | 
					
 | 
				
			||||||
.. _`simpletest`:
 | 
					.. _`simpletest`:
 | 
				
			||||||
 | 
					
 | 
				
			||||||
| 
						 | 
					
 | 
				
			||||||
		Loading…
	
		Reference in New Issue