[Doppins] Upgrade dependency pytest to ==5.1.1 #236
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
A new version was just released of
pytest
, so Doppinshas upgraded your project's dependency ranges.
Make sure that it doesn't break anything, and happy merging!![:shipit: :shipit:](https://github.githubassets.com/images/icons/emoji/shipit.png)
Upgraded pytest from
==3.2.3
to==5.1.1
Changelog:
Version 5.1.1
pytest 5.1.1 (2019-08-20)
Bug Fixes
(
https://github.com/pytest-dev/pytest/issues/5751`): FixedTypeError
when importing pytest on Python 3.5.0 and 3.5.1.Version 5.1.0
pytest 5.1.0 (2019-08-15)
Removals
`#5180
(
https://github.com/pytest-dev/pytest/issues/5180`): As perour policy, the following features have been deprecated in the 4.X
series and are now removed:
Request.getfuncargvalue
: useRequest.getfixturevalue
instead.
pytest.raises
andpytest.warns
no longer support strings asthe second argument.
message
parameter ofpytest.raises
.pytest.raises
,pytest.warns
andParameterSet.param
now usenative keyword-only syntax. This might change the exception
message from previous versions, but they still raise
TypeError
on unknown keyword arguments as before.
pytest.config
global variable.tmpdir_factory.ensuretemp
method.pytest_logwarning
hook.RemovedInPytest4Warning
warning type.request
is now a reserved name for fixtures.For more information consult Deprecations and
Removals in
the docs.
`#5565
(
https://github.com/pytest-dev/pytest/issues/5565`): Removedunused support code for
unittest2.
The
unittest2
backport module is no longer necessary since Python3.3+, and the small amount of code in pytest to support it also
doesn't seem to be used: after removed, all tests still pass
unchanged.
Although our policy is to introduce a deprecation period before
removing any features or support for third party libraries, because
this code is apparently not used at all (even if
unittest2
is usedby a test suite executed by pytest), it was decided to remove it in
this release.
If you experience a regression because of this, please file an
issue.
`#5615
(
https://github.com/pytest-dev/pytest/issues/5615`):pytest.fail
,pytest.xfail
andpytest.skip
no longer supportbytes for the message argument.
This was supported for Python 2 where it was tempting to use
"message"
instead ofu"message"
.Python 3 code is unlikely to pass
bytes
to these functions. If youdo, please decode it to an
str
beforehand.Features
(
https://github.com/pytest-dev/pytest/issues/5564`): NewConfig.invocation_args
attribute containing the unchangedarguments passed to
pytest.main()
.(
https://github.com/pytest-dev/pytest/issues/5576`): NewNUMBER
option for doctests to ignore irrelevant differences in
floating-point numbers. Inspired by Sébastien Boisgérault's
numtest extension for
doctest.
Improvements
`#5471
(
https://github.com/pytest-dev/pytest/issues/5471`): JUnitXML now includes a timestamp and hostname in the testsuite tag.
`#5707
(
https://github.com/pytest-dev/pytest/issues/5707`): Timetaken to run the test suite now includes a human-readable
representation when it takes over 60 seconds, for example:
Bug Fixes
(
https://github.com/pytest-dev/pytest/issues/4344`): FixRuntimeError/StopIteration when trying to collect package with
"__init__.py" only.
(
https://github.com/pytest-dev/pytest/issues/5115`): Warningsissued during
pytest_configure
are explicitly not treated aserrors, even if configured as such, because it otherwise completely
breaks pytest.
(
https://github.com/pytest-dev/pytest/issues/5477`): The XMLfile produced by
--junitxml
now correctly contain a<testsuites>
root element.
(
https://github.com/pytest-dev/pytest/issues/5523`): Fixedusing multiple short options together in the command-line (for
example
-vs
) in Python 3.8+.(
https://github.com/pytest-dev/pytest/issues/5524`): Fixissue where
tmp_path
andtmpdir
would not remove directoriescontaining files marked as read-only, which could lead to pytest
crashing when executed a second time with the
--basetemp
option.(
https://github.com/pytest-dev/pytest/issues/5537`): Replaceimportlib_metadata
backport withimportlib.metadata
from thestandard library on Python 3.8+.
(
https://github.com/pytest-dev/pytest/issues/5578`): Improvetype checking for some exception-raising functions (
pytest.xfail
,pytest.skip
, etc) so they provide better error messages when usersmeant to use marks (for example
@pytest`.xfail` instead of
@pytest.mark.xfail
).(
https://github.com/pytest-dev/pytest/issues/5606`): Fixedinternal error when test functions were patched with objects that
cannot be compared for truth values against others, like
numpy
arrays.
(
https://github.com/pytest-dev/pytest/issues/5634`):pytest.exit
is now correctly handled inunittest
cases. Thismakes
unittest
cases handlequit
from pytest's pdb correctly.(
https://github.com/pytest-dev/pytest/issues/5650`): Improvedoutput when parsing an ini configuration file fails.
(
https://github.com/pytest-dev/pytest/issues/5701`): Fixcollection of
staticmethod
objects defined withfunctools.partial
.(
https://github.com/pytest-dev/pytest/issues/5734`): Skipasync generator test functions, and update the warning message to
refer to
async def
functions.Improved Documentation
(
https://github.com/pytest-dev/pytest/issues/5669`): Adddocstring for
Testdir.copy_example
.Trivial/Internal Changes
(
https://github.com/pytest-dev/pytest/issues/5095`): XMLfiles of the
xunit2
family are now validated against the schema bypytest's own test suite to avoid future regressions.
(
https://github.com/pytest-dev/pytest/issues/5516`): Cachenode splitting function which can improve collection performance in
very large test suites.
(
https://github.com/pytest-dev/pytest/issues/5603`):Simplified internal
SafeRepr
class and removed some dead code.(
https://github.com/pytest-dev/pytest/issues/5664`): Wheninvoking pytest's own testsuite with
PYTHONDONTWRITEBYTECODE=1
,the
test_xfail_handling
test no longer fails.(
https://github.com/pytest-dev/pytest/issues/5684`): Replacemanual handling of
OSError.errno
in the codebase by newOSError
subclasses (
PermissionError
,FileNotFoundError
, etc.).Version 5.0.1
pytest 5.0.1 (2019-07-04)
Bug Fixes
(
https://github.com/pytest-dev/pytest/issues/5479`): Improvequoting in
raises
match failure message.(
https://github.com/pytest-dev/pytest/issues/5523`): Fixedusing multiple short options together in the command-line (for
example
-vs
) in Python 3.8+.(
https://github.com/pytest-dev/pytest/issues/5547`):--step-wise
now handlesxfail(strict=True)
markers properly.Improved Documentation
(
https://github.com/pytest-dev/pytest/issues/5517`): Improve"Declaring new hooks" section in chapter "Writing Plugins"
Version 4.6.5
Bug Fixes
#4344
(https://github.com/pytest-dev/pytest/issues/4344
): Fix RuntimeError/StopIteration when trying to collect package with "init.py" only.#5478
(https://github.com/pytest-dev/pytest/issues/5478
): Fix encode error when using unicode strings in exceptions withpytest.raises
.#5524
(https://github.com/pytest-dev/pytest/issues/5524
): Fix issue wheretmp_path
andtmpdir
would not remove directories containing files marked as read-only,which could lead to pytest crashing when executed a second time with the
--basetemp
option.#5547
(https://github.com/pytest-dev/pytest/issues/5547
):--step-wise
now handlesxfail(strict=True)
markers properly.#5650
(https://github.com/pytest-dev/pytest/issues/5650
): Improved output when parsing an ini configuration file fails.