Skip to content
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

Bump mock from 3.0.5 to 4.0.0 #15

Closed
wants to merge 1 commit into from

Conversation

dependabot-preview[bot]
Copy link

Bumps mock from 3.0.5 to 4.0.0.

Changelog

Sourced from mock's changelog.

4.0.0

  • No Changes from 4.0.0b1.

4.0.0b1

  • The release is a fresh cut of cpython's 4a686504__. All changes to mock from that commit and before are included in this release along with the subsequent changes listed below.

    __ python/cpython@4a68650

  • Issue #37972: Subscripts to the unittest.mock.call objects now receive the same chaining mechanism as any other custom attributes, so that the following usage no longer raises a `TypeError`:

    call().foo().__getitem__('bar')

    Patch by blhsing

  • Issue #38839: Fix some unused functions in tests. Patch by Adam Johnson.

  • Issue #39485: Fix a bug in unittest.mock.create_autospec that would complain about the wrong number of arguments for custom descriptors defined in an extension module returning functions.

  • Issue #39082: Allow AsyncMock to correctly patch static/class methods

  • Issue #38093: Fixes AsyncMock so it doesn't crash when used with AsyncContextManagers or AsyncIterators.

  • Issue #38859: AsyncMock now returns StopAsyncIteration on the exaustion of a side_effects iterable. Since PEP-479 its Impossible to raise a StopIteration exception from a coroutine.

  • Issue #38163: Child mocks will now detect their type as either synchronous or asynchronous, asynchronous child mocks will be AsyncMocks and synchronous child mocks will be either MagicMock or Mock (depending on their parent type).

  • Issue #38473: Use signature from inner mock for autospecced methods attached with unittest.mock.attach_mock. Patch by Karthikeyan Singaravelan.

  • Issue #38136: Changes AsyncMock call count and await count to be two different counters. Now await count only counts when a coroutine has been awaited, not when it has been called, and vice-versa. Update the documentation around this.

  • Issue #37555: Fix NonCallableMock._call_matcher returning tuple instead of _Call object when self._spec_signature exists. Patch by Elizabeth Uselton

  • Issue #37251: Remove __code__ check in AsyncMock that incorrectly evaluated function specs as async objects but failed to evaluate classes with __await__ but no __code__ attribute defined as async objects.

  • Issue #38669: Raise TypeError when passing target as a string with unittest.mock.patch.object.

  • Issue #25597: Ensure, if wraps is supplied to unittest.mock.MagicMock, it is used to calculate return values for the magic methods instead of using the default return values. Patch by Karthikeyan Singaravelan.

  • Issue #38108: Any synchronous magic methods on an AsyncMock now return a MagicMock. Any asynchronous magic methods on a MagicMock now return an AsyncMock.

  • Issue #21478: Record calls to parent when autospecced object is attached to a mock using unittest.mock.attach_mock. Patch by Karthikeyan Singaravelan.

  • Issue #38857: AsyncMock fix for return values that are awaitable types. This also covers side_effect iterable values that happend to be awaitable, and wraps callables that return an awaitable type. Before these awaitables were being awaited instead of being returned as is.

  • Issue #38932: Mock fully resets child objects on reset_mock(). Patch by Vegard Stikbakke

  • Issue #37685: Fixed __eq__, __lt__ etc implementations in some classes. They now return NotImplemented for unsupported type of the other operand. This allows the other operand to play role (for example the equality comparison with ~unittest.mock.ANY will return True).

  • Issue #37212: unittest.mock.call now preserves the order of keyword arguments in repr output. Patch by Karthikeyan Singaravelan.

  • Issue #37828: Fix default mock name in unittest.mock.Mock.assert_called exceptions. Patch by Abraham Toriz Cruz.

  • Issue #36871: Improve error handling for the assert_has_calls and assert_has_awaits methods of mocks. Fixed a bug where any errors encountered while binding the expected calls to the mock's spec were silently swallowed, leading to misleading error output.

  • Issue #21600: Fix mock.patch.stopall to stop active patches that were created with mock.patch.dict.

  • Issue #38161: Removes _AwaitEvent from AsyncMock.

  • Issue #36871: Ensure method signature is used instead of constructor signature of a class while asserting mock object against method calls. Patch by Karthikeyan Singaravelan.

Commits

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)
  • Pull request limits (per update run and/or open at any time)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Bumps [mock](https://github.com/testing-cabal/mock) from 3.0.5 to 4.0.0.
- [Release notes](https://github.com/testing-cabal/mock/releases)
- [Changelog](https://github.com/testing-cabal/mock/blob/master/CHANGELOG.rst)
- [Commits](testing-cabal/mock@3.0.5...4.0.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 Feb 6, 2020
@coveralls
Copy link

Coverage Status

Coverage remained the same at 87.665% when pulling d0004a3 on dependabot/pip/mock-4.0.0 into 8d10b9a on master.

@dependabot-preview
Copy link
Author

Superseded by #16.

@dependabot-preview dependabot-preview bot deleted the dependabot/pip/mock-4.0.0 branch February 7, 2020 05:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant