Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

build(deps-dev): update pytest-mock requirement from ^1.10 to ^2.0 #111

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
woile merged 1 commit into master from dependabot/pip/pytest-mock-tw-2.0
Jan 12, 2020

Conversation

Copy link
Contributor

@dependabot-preview dependabot-preview bot commented Jan 6, 2020

Updates the requirements on pytest-mock to permit the latest version.

Release notes

Sourced from pytest-mock's releases.

2.0.0 (2020年01月04日)

Breaking Changes

  • mocker.spy attributes for tracking returned values and raised exceptions of its spied functions are now called spy_return and spy_exception, instead of reusing the existing MagicMock attributes return_value and side_effect.

    Version 1.13 introduced a serious regression: after a spied function using mocker.spy raises an exception, further calls to the spy will not call the spied function, always raising the first exception instead: assigning to side_effect causes unittest.mock to behave this way (#175).

  • The deprecated mock alias to the mocker fixture has finally been removed.

Changelog

Sourced from pytest-mock's changelog.

2.0.0 (2020年01月04日)

Breaking Changes

  • mocker.spy attributes for tracking returned values and raised exceptions of its spied functions are now called spy_return and spy_exception, instead of reusing the existing MagicMock attributes return_value and side_effect.

    Version 1.13 introduced a serious regression: after a spied function using mocker.spy raises an exception, further calls to the spy will not call the spied function, always raising the first exception instead: assigning to side_effect causes unittest.mock to behave this way (#175).

  • The deprecated mock alias to the mocker fixture has finally been removed.

1.13.0 (2019年12月05日)

  • The object returned by mocker.spy now also tracks any side effect of the spied method/function.

1.12.1 (2019年11月20日)

  • Fix error if mocker.patch is used in code where the source file is not available, for example stale .pyc files (#169).

1.12.0 (2019年11月19日)

  • Now all patch functions also raise a ValueError when used as a context-manager. Thanks @AlexGascon for the PR (#168).

1.11.2 (2019年10月19日)

  • The pytest introspection follows message is no longer shown if there is no pytest introspection (#154). Thanks @The-Compiler for the report.
  • mocker now raises a ValueError when used as a context-manager. Thanks @binarymason for the PR (#165).

1.11.1 (2019年10月04日)

  • Fix mocker.spy on Python 2 when used on non-function objects which implement __call__ (#157). Thanks @pbasista for the report.

1.11.0

  • The object returned by mocker.spy now also tracks the return value of the spied method/function.

1.10.4

  • Fix plugin when 'terminal' plugin is disabled

1.10.3

... (truncated)
Commits
  • ccb76e5 Drop deprecated 'mock' alias to 'mocker'
  • fd02462 Change spy attributes to 'spy_return' and 'spy_exception'
  • 7bddcd5 Merge pull request #173 from inderpreet99/spy-exceptions
  • 895efb1 Add date to changelog for version 1.13.0
  • 567e053 Add docs for side effect feature on spies
  • 50f99e5 Record exceptions as side effects for spies
  • b3e0ad5 Black linting
  • 0df91f9 Add spy exception catching
  • 25de852 Store raised exceptions in return_value for spies
  • 2655441 Update coverage badge in README.rst (#172)
  • Additional commits viewable 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 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)
  • 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)

Updates the requirements on [pytest-mock](https://github.com/pytest-dev/pytest-mock) to permit the latest version.
- [Release notes](https://github.com/pytest-dev/pytest-mock/releases)
- [Changelog](https://github.com/pytest-dev/pytest-mock/blob/master/CHANGELOG.rst)
- [Commits](pytest-dev/pytest-mock@v1.10.0...v2.0.0)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
Copy link

codecov bot commented Jan 6, 2020
edited
Loading

Codecov Report

❗ No coverage uploaded for pull request base (master@ee0188e). Click here to learn what that means.
The diff coverage is n/a.

Impacted file tree graph

@@ Coverage Diff @@
## master #111 +/- ##
========================================
 Coverage ? 83.4% 
========================================
 Files ? 32 
 Lines ? 711 
 Branches ? 0 
========================================
 Hits ? 593 
 Misses ? 118 
 Partials ? 0
Flag Coverage Δ
#unittests 83.4% <ø> (?)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ee0188e...23c9a9a. Read the comment docs.

@woile woile merged commit b168380 into master Jan 12, 2020
@dependabot-preview dependabot-preview bot deleted the dependabot/pip/pytest-mock-tw-2.0 branch January 12, 2020 10:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

1 participant

AltStyle によって変換されたページ (->オリジナル) /