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 pytest-mock from 1.11.1 to 3.6.0 in /requirements #13

Closed

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github May 1, 2021

Bumps pytest-mock from 1.11.1 to 3.6.0.

Release notes

Sourced from pytest-mock's releases.

3.3.1 (2020-08-24)

  • Introduce MockFixture as an alias to MockerFixture.

    Before 3.3.0, the fixture class was named MockFixture, but was renamed to MockerFixture to better match the mocker fixture. While not officially part of the API, it was later discovered that this broke the code of some users which already imported pytest_mock.MockFixture for type annotations, so we decided to reintroduce the name as an alias.

    Note however that this is just a stop gap measure, and new code should use MockerFixture for type annotations.

  • Improved typing for MockerFixture.patch (#201). Thanks @​srittau for the PR.

3.3.0 (2020-08-21)

  • pytest-mock now includes inline type annotations and exposes them to user programs. The mocker fixture returns pytest_mock.MockerFixture, which can be used to annotate your tests:

    from pytest_mock import MockerFixture
    def test_foo(mocker: MockerFixture) -> None:
    ...

    The type annotations were developed against mypy version 0.782, the minimum version supported at the moment. If you run into an error that you believe to be incorrect, please open an issue.

    Many thanks to @​staticdev for providing the initial patch #199.

3.2.0 (2020-07-11)

  • AsyncMock is now exposed in mocker and supports provides assertion introspection similar to Mock objects.

    Added by @​tirkarthi in #197.

3.1.1 (2020-05-31)

  • Fixed performance regression caused by the ValueError raised when mocker is used as context manager (#191).

3.1.0 (2020-04-18)

  • New mocker fixtures added that allow using mocking functionality in other scopes:

    • class_mocker
    • module_mocker
    • package_mocker
    • session_mocker

    Added by @​scorphus in #182.

3.0.0 (2020-03-31)

  • Python 2.7 and 3.4 are no longer supported. Users using pip 9 or later will install a compatible version automatically.
  • mocker.spy now also works with async def functions (#179). Thanks @​frankie567 for the PR!

... (truncated)

Changelog

Sourced from pytest-mock's changelog.

3.6.0 (2021-04-24)

  • pytest-mock no longer supports Python 3.5.

  • Correct type annotations for mocker.patch.object to also include the string form. Thanks @plannigan_ for the PR ([#235](https://github.com/pytest-dev/pytest-mock/issues/235)_).

  • reset_all now supports return_value and side_effect keyword arguments. Thanks @alex-marty_ for the PR ([#214](https://github.com/pytest-dev/pytest-mock/issues/214)_).

.. _@​alex-marty: https://github.com/alex-marty .. _@​plannigan: https://github.com/plannigan .. _#214: pytest-dev/pytest-mock#214 .. _#235: pytest-dev/pytest-mock#235

3.5.1 (2021-01-10)

  • Use inspect.getattr_static instead of resorting to object.__getattribute__ magic. This should better comply with objects which implement a custom descriptor protocol. Thanks @yesthesoup_ for the PR ([#224](https://github.com/pytest-dev/pytest-mock/issues/224)_).

.. _@​yesthesoup: https://github.com/yesthesoup .. _#224: pytest-dev/pytest-mock#224

3.5.0 (2021-01-04)

  • Now all patch functions will emit a warning instead of raising a ValueError when used as a context-manager. Thanks @iforapsy_ for the PR ([#221](https://github.com/pytest-dev/pytest-mock/issues/221)_).

  • Additionally, mocker.patch.context_manager is available when the user intends to mock a context manager (for example threading.Lock object), which will not emit that warning.

.. _@​iforapsy: https://github.com/iforapsy .. _#221: pytest-dev/pytest-mock#221

3.4.0 (2020-12-15)

  • Add mock.seal alias to the mocker fixture ([#211](https://github.com/pytest-dev/pytest-mock/issues/211)). Thanks @coiax for the PR.

  • Fixed spying on exceptions not covered by the Exception superclass ([#215](https://github.com/pytest-dev/pytest-mock/issues/215)), like KeyboardInterrupt -- PR [#216](https://github.com/pytest-dev/pytest-mock/issues/216) by @webknjaz_.

    Before the fix, both spy_return and spy_exception were always assigned to None whenever such an exception happened. And after this fix,

... (truncated)

Commits
  • 4716752 Drop Python 3.5 support
  • 3425616 Move setup.cfg to mypy.ini
  • c3e9aa1 Add resetall() arguments (#214)
  • 28ef007 Merge pull request #235 from plannigan/patch_dict_annotations
  • 6e5600d Update changelog
  • 55e4be7 Correct type annotations in patch.dict()
  • be33132 Merge pull request #233 from fhightower/2021-march-fix-broken-pytest-links
  • 58d7b2e Fixing link to pytest assertions
  • 9d98658 Merge pull request #232 from pytest-dev/pre-commit-ci-update-config
  • f01618d [pre-commit.ci] pre-commit autoupdate
  • 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 dependabot bot added the dependencies Pull requests that update a dependency file label May 1, 2021
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Jun 1, 2021

Superseded by #14.

@dependabot dependabot bot closed this Jun 1, 2021
@dependabot dependabot bot deleted the dependabot/pip/requirements/pytest-mock-3.6.0 branch June 1, 2021 07:53
keithjgrant pushed a commit that referenced this pull request Apr 17, 2023
check label permission and fix lint (#13)

* set created by and launch type correctly

This makes "launched_by" get computed right in the tests.

Mysteriously this seemed to work from API browser, but
this seems more correct to have it work this way, and makes
tests actually work.

For "manual" launch types the attribute used to populate "launched_by"
is "created_by". And we already have "is_bulk_job" to indicate that the
job is a bulk job. So lets just use this.

* check label is in an organization you can read
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.

0 participants