Update pytest requirement from ~=4.1.0 to ~=4.1.1

[dependabot-preview]

Updates the requirements on pytest to permit the latest version.

Changelog

Sourced from pytest's changelog.

pytest 4.1.1 (2019-01-12)

Bug Fixes

• #2256 <https://github-redirect.dependabot.com/pytest-dev/pytest/issues/2256>_: Show full repr with assert a==b and -vv.

• #3456 <https://github-redirect.dependabot.com/pytest-dev/pytest/issues/3456>_: Extend Doctest-modules to ignore mock objects.

• #4617 <https://github-redirect.dependabot.com/pytest-dev/pytest/issues/4617>_: Fixed pytest.warns bug when context manager is reused (e.g. multiple parametrization).

• #4631 <https://github-redirect.dependabot.com/pytest-dev/pytest/issues/4631>_: Don't rewrite assertion when __getattr__ is broken

Improved Documentation

• #3375 <https://github-redirect.dependabot.com/pytest-dev/pytest/issues/3375>_: Document that using setup.cfg may crash other tools or cause hard to track down problems because it uses a different parser than pytest.ini or tox.ini files.

Trivial/Internal Changes

• #4602 <https://github-redirect.dependabot.com/pytest-dev/pytest/issues/4602>_: Uninstall hypothesis in regen tox env.

pytest 4.1.0 (2019-01-05)

Removals

• #2169 <https://github-redirect.dependabot.com/pytest-dev/pytest/issues/2169>_: pytest.mark.parametrize: in previous versions, errors raised by id functions were suppressed and changed into warnings. Now the exceptions are propagated, along with a pytest message informing the node, parameter value and index where the exception occurred.

• #3078 <https://github-redirect.dependabot.com/pytest-dev/pytest/issues/3078>_: Remove legacy internal warnings system: config.warn, Node.warn. The pytest_logwarning now issues a warning when implemented.

  See our docs <https://docs.pytest.org/en/latest/deprecations.html#config-warn-and-node-warn>__ on information on how to update your code.

• #3079 <https://github-redirect.dependabot.com/pytest-dev/pytest/issues/3079>_: Removed support for yield tests - they are fundamentally broken because they don't support fixtures properly since collection and test execution were separated.

  See our docs <https://docs.pytest.org/en/latest/deprecations.html#yield-tests>__ on information on how to update your code.

... (truncated)

Commits

• See full diff in compare view

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 cancel merge will cancel a previously requested merge
• @dependabot reopen will reopen this PR if it is closed
• @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major 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.