Skip to content
This repository has been archived by the owner on Aug 19, 2019. It is now read-only.

Bump pytest from 5.0.1 to 5.1.0 #85

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps pytest from 5.0.1 to 5.1.0.

Release notes

Sourced from pytest's releases.

5.1.0

pytest 5.1.0 (2019-08-15)

Removals

  • #5180: As per
    our policy, the following features have been deprecated in the 4.X
    series and are now removed:

    • Request.getfuncargvalue: use Request.getfixturevalue
      instead.
    • pytest.raises and pytest.warns no longer support strings as
      the second argument.
    • message parameter of pytest.raises.
    • pytest.raises, pytest.warns and ParameterSet.param now use
      native 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: Removed
    unused support code for
    unittest2.

    The unittest2 backport module is no longer necessary since Python
    3.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 used
    by 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:
    pytest.fail, pytest.xfail and pytest.skip no longer support

... (truncated)
Changelog

Sourced from pytest's changelog.

pytest 5.1.0 (2019-08-15)

Removals

  • #5180: As per our policy, the following features have been deprecated in the 4.X series and are now removed:

    • Request.getfuncargvalue: use Request.getfixturevalue instead.
    • pytest.raises and pytest.warns no longer support strings as the second argument.
    • message parameter of pytest.raises.
    • pytest.raises, pytest.warns and ParameterSet.param now use native 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: Removed unused support code for unittest2.

    The unittest2 backport module is no longer necessary since Python 3.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 used by 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: pytest.fail, pytest.xfail and pytest.skip no longer support bytes for the message argument.

    This was supported for Python 2 where it was tempting to use "message" instead of u"message".

    Python 3 code is unlikely to pass bytes to these functions. If you do, please decode it to an str beforehand.

Features

  • #5564: New Config.invocation_args attribute containing the unchanged arguments passed to pytest.main().
  • #5576: New NUMBER option for doctests to ignore irrelevant differences in floating-point numbers. Inspired by Sébastien Boisgérault's numtest extension for doctest.

Improvements

  • #5471: JUnit XML now includes a timestamp and hostname in the testsuite tag.

  • #5707: Time taken to run the test suite now includes a human-readable representation when it takes over 60 seconds, for example:

    ===== 2 failed in 102.70s (0:01:42) =====
    

Bug Fixes

... (truncated)
Commits
  • eaf7ce9 Preparing release version 5.1.0
  • 409d61b Merge remote-tracking branch 'upstream/master' into release-5.1.0
  • 44c10db Merge pull request #5746 from blueyed/codecov-comment-off
  • 0f11a7a Merge master into features (#5744)
  • d50198a ci: add codecov.yml to turn comments off
  • ac052a9 reword a parametrize example sentence (#5745)
  • f4a84a8 reword a parametrize example sentence
  • 1049a38 Fix wording as suggested in review of #5741
  • d7f0825 Merge remote-tracking branch 'upstream/master' into mm
  • 2d613a0 Async result warn (#5742)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

Bumps [pytest](https://github.com/pytest-dev/pytest) from 5.0.1 to 5.1.0.
- [Release notes](https://github.com/pytest-dev/pytest/releases)
- [Changelog](https://github.com/pytest-dev/pytest/blob/master/CHANGELOG.rst)
- [Commits](pytest-dev/pytest@5.0.1...5.1.0)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Aug 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants