Preparing release version 3.2.2
This commit is contained in:
parent
549f5c1a47
commit
c52f87ede3
|
@ -8,6 +8,53 @@
|
||||||
|
|
||||||
.. towncrier release notes start
|
.. towncrier release notes start
|
||||||
|
|
||||||
|
Pytest 3.2.2 (2017-09-06)
|
||||||
|
=========================
|
||||||
|
|
||||||
|
Bug Fixes
|
||||||
|
---------
|
||||||
|
|
||||||
|
- Calling the deprecated `request.getfuncargvalue()` now shows the source of
|
||||||
|
the call. (`#2681 <https://github.com/pytest-dev/pytest/issues/2681>`_)
|
||||||
|
|
||||||
|
- Allow tests declared as ``@staticmethod`` to use fixtures. (`#2699
|
||||||
|
<https://github.com/pytest-dev/pytest/issues/2699>`_)
|
||||||
|
|
||||||
|
- Fixed edge-case during collection: attributes which raised ``pytest.fail``
|
||||||
|
when accessed would abort the entire collection. (`#2707
|
||||||
|
<https://github.com/pytest-dev/pytest/issues/2707>`_)
|
||||||
|
|
||||||
|
- Fix ``ReprFuncArgs`` with mixed unicode and UTF-8 args. (`#2731
|
||||||
|
<https://github.com/pytest-dev/pytest/issues/2731>`_)
|
||||||
|
|
||||||
|
|
||||||
|
Improved Documentation
|
||||||
|
----------------------
|
||||||
|
|
||||||
|
- In examples on working with custom markers, add examples demonstrating the
|
||||||
|
usage of ``pytest.mark.MARKER_NAME.with_args`` in comparison with
|
||||||
|
``pytest.mark.MARKER_NAME.__call__`` (`#2604
|
||||||
|
<https://github.com/pytest-dev/pytest/issues/2604>`_)
|
||||||
|
|
||||||
|
- In one of the simple examples, use `pytest_collection_modifyitems()` to skip
|
||||||
|
tests based on a command-line option, allowing its sharing while preventing a
|
||||||
|
user error when acessing `pytest.config` before the argument parsing. (`#2653
|
||||||
|
<https://github.com/pytest-dev/pytest/issues/2653>`_)
|
||||||
|
|
||||||
|
|
||||||
|
Trivial/Internal Changes
|
||||||
|
------------------------
|
||||||
|
|
||||||
|
- Fixed minor error in 'Good Practices/Manual Integration' code snippet.
|
||||||
|
(`#2691 <https://github.com/pytest-dev/pytest/issues/2691>`_)
|
||||||
|
|
||||||
|
- Fixed typo in goodpractices.rst. (`#2721
|
||||||
|
<https://github.com/pytest-dev/pytest/issues/2721>`_)
|
||||||
|
|
||||||
|
- Improve user guidance regarding ``--resultlog`` deprecation. (`#2739
|
||||||
|
<https://github.com/pytest-dev/pytest/issues/2739>`_)
|
||||||
|
|
||||||
|
|
||||||
Pytest 3.2.1 (2017-08-08)
|
Pytest 3.2.1 (2017-08-08)
|
||||||
=========================
|
=========================
|
||||||
|
|
||||||
|
|
|
@ -1 +0,0 @@
|
||||||
In examples on working with custom markers, add examples demonstrating the usage of ``pytest.mark.MARKER_NAME.with_args`` in comparison with ``pytest.mark.MARKER_NAME.__call__``
|
|
|
@ -1 +0,0 @@
|
||||||
In one of the simple examples, use `pytest_collection_modifyitems()` to skip tests based on a command-line option, allowing its sharing while preventing a user error when acessing `pytest.config` before the argument parsing.
|
|
|
@ -1 +0,0 @@
|
||||||
Calling the deprecated `request.getfuncargvalue()` now shows the source of the call.
|
|
|
@ -1 +0,0 @@
|
||||||
Fixed minor error in 'Good Practices/Manual Integration' code snippet.
|
|
|
@ -1 +0,0 @@
|
||||||
Allow tests declared as ``@staticmethod`` to use fixtures.
|
|
|
@ -1 +0,0 @@
|
||||||
Fixed edge-case during collection: attributes which raised ``pytest.fail`` when accessed would abort the entire collection.
|
|
|
@ -1 +0,0 @@
|
||||||
Fixed typo in goodpractices.rst.
|
|
|
@ -1 +0,0 @@
|
||||||
Fix ``ReprFuncArgs`` with mixed unicode and UTF-8 args.
|
|
|
@ -1 +0,0 @@
|
||||||
Improve user guidance regarding ``--resultlog`` deprecation.
|
|
|
@ -6,6 +6,7 @@ Release announcements
|
||||||
:maxdepth: 2
|
:maxdepth: 2
|
||||||
|
|
||||||
|
|
||||||
|
release-3.2.2
|
||||||
release-3.2.1
|
release-3.2.1
|
||||||
release-3.2.0
|
release-3.2.0
|
||||||
release-3.1.3
|
release-3.1.3
|
||||||
|
|
|
@ -0,0 +1,28 @@
|
||||||
|
pytest-3.2.2
|
||||||
|
=======================================
|
||||||
|
|
||||||
|
pytest 3.2.2 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 http://doc.pytest.org/en/latest/changelog.html.
|
||||||
|
|
||||||
|
Thanks to all who contributed to this release, among them:
|
||||||
|
|
||||||
|
* Andreas Pelme
|
||||||
|
* Antonio Hidalgo
|
||||||
|
* Bruno Oliveira
|
||||||
|
* Felipe Dau
|
||||||
|
* Fernando Macedo
|
||||||
|
* Jesús Espino
|
||||||
|
* Joan Massich
|
||||||
|
* Joe Talbott
|
||||||
|
* Kirill Pinchuk
|
||||||
|
* Ronny Pfannschmidt
|
||||||
|
* Xuan Luong
|
||||||
|
|
||||||
|
|
||||||
|
Happy testing,
|
||||||
|
The pytest Development Team
|
|
@ -393,6 +393,7 @@ The ``--markers`` option always gives you a list of available markers::
|
||||||
@pytest.mark.tryfirst: mark a hook implementation function such that the plugin machinery will try to call it first/as early as possible.
|
@pytest.mark.tryfirst: mark a hook implementation function such that the plugin machinery will try to call it first/as early as possible.
|
||||||
|
|
||||||
@pytest.mark.trylast: mark a hook implementation function such that the plugin machinery will try to call it last/as late as possible.
|
@pytest.mark.trylast: mark a hook implementation function such that the plugin machinery will try to call it last/as late as possible.
|
||||||
|
|
||||||
|
|
||||||
.. _`passing callables to custom markers`:
|
.. _`passing callables to custom markers`:
|
||||||
|
|
||||||
|
@ -430,9 +431,9 @@ However, if there is a callable as the single positional argument with no keywor
|
||||||
The output is as follows::
|
The output is as follows::
|
||||||
|
|
||||||
$ pytest -q -s
|
$ pytest -q -s
|
||||||
Marker info name=my_marker args=(<function hello_world at 0x7f0b7b058bf8>,) kwars={}
|
Marker info name=my_marker args=(<function hello_world at 0xdeadbeef>,) kwars={}
|
||||||
.
|
.
|
||||||
1 passed in 0.01 seconds
|
1 passed in 0.12 seconds
|
||||||
|
|
||||||
We can see that the custom marker has its argument set extended with the function ``hello_world``. This is the key different between creating a custom marker as a callable, which invokes ``__call__`` behind the scenes, and using ``with_args``.
|
We can see that the custom marker has its argument set extended with the function ``hello_world``. This is the key different between creating a custom marker as a callable, which invokes ``__call__`` behind the scenes, and using ``with_args``.
|
||||||
|
|
||||||
|
|
|
@ -358,7 +358,7 @@ get on the terminal - we are working on that)::
|
||||||
> int(s)
|
> int(s)
|
||||||
E ValueError: invalid literal for int() with base 10: 'qwe'
|
E ValueError: invalid literal for int() with base 10: 'qwe'
|
||||||
|
|
||||||
<0-codegen $PYTHON_PREFIX/lib/python3.5/site-packages/_pytest/python_api.py:570>:1: ValueError
|
<0-codegen $PYTHON_PREFIX/lib/python3.5/site-packages/_pytest/python_api.py:579>:1: ValueError
|
||||||
_______ TestRaises.test_raises_doesnt ________
|
_______ TestRaises.test_raises_doesnt ________
|
||||||
|
|
||||||
self = <failure_demo.TestRaises object at 0xdeadbeef>
|
self = <failure_demo.TestRaises object at 0xdeadbeef>
|
||||||
|
|
Loading…
Reference in New Issue