Changelog
*Sourced from [pytest-qt's changelog](https://github.com/pytest-dev/pytest-qt/blob/master/CHANGELOG.rst).*
> 3.2.2 (2018-12-13)
> ------------------
>
> - Fix Off-by-one error in ``modeltester`` (`#249`_). Thanks `[**ext-jmmugnes**](https://github.com/ext-jmmugnes)`_ for the PR.
>
> .. _#249: https://github-redirect.dependabot.com/pytest-dev/pytest-qt/pull/249
>
>
> 3.2.1 (2018-10-01)
> ------------------
>
> - Fixed compatibility with PyQt5 5.11.3
>
> 3.2.0 (2018-09-26)
> ------------------
>
> - The ``CallbackBlocker`` returned by ``qtbot.waitCallback()`` now has a new
> ``assert_called_with(...)`` convenience method.
>
> 3.1.0 (2018-09-23)
> ------------------
>
> - If Qt's model tester implemented in C++ is available (PyQt5 5.11 or newer),
> the ``qtmodeltester`` fixture now uses that instead of the Python
> implementation. This can be turned off by passing ``force_py=True`` to
> ``qtmodeltester.check()``.
>
> - The Python code used by ``qtmodeltester`` is now based on the latest Qt
> modeltester. This also means that the ``data_display_may_return_none``
> attribute for ``qtmodeltester`` isn't used anymore.
>
> - New ``qtbot.waitCallback()`` method that returns a ``CallbackBlocker``, which
> can be used to wait for a callback to be called.
>
> - ``qtbot.assertNotEmitted`` now has a new ``wait`` parameter which can be used
> to make sure asynchronous signals aren't emitted by waiting after the code in
> the ``with`` block finished.
>
> - The ``qt_wait_signal_raising`` option was renamed to ``qt_default_raising``.
> The old name continues to work, but is deprecated.
>
> - The docs still referred to ``SignalTimeoutError`` in some places, despite it
> being renamed to ``TimeoutError`` in the 2.1 release. This is now corrected.
>
> - Improve debugging output when no Qt wrapper was found.
>
> - When no context is available for warnings on Qt 5, no ``None:None:0`` line is
> shown anymore.
>
> - The ``no_qt_log`` marker is now registered with pytest so ``--strict`` can be
> ... (truncated)
Commits
- [`83ad838`](https://github.com/pytest-dev/pytest-qt/commit/83ad838be68625ecc33cabaeb23cb776c8de30a9) Update CHANGELOG for 3.2.2
- [`05301c5`](https://github.com/pytest-dev/pytest-qt/commit/05301c58e548ed76cb76b589f6f64b1d1ce9a3fe) Merge pull request [#249](https://github-redirect.dependabot.com/pytest-dev/pytest-qt/issues/249) from ext-jmmugnes/patch-1
- [`6680570`](https://github.com/pytest-dev/pytest-qt/commit/66805707631669add3ea3ead1668b31110128693) fixed bug [#248](https://github-redirect.dependabot.com/pytest-dev/pytest-qt/issues/248)
- [`0f74d72`](https://github.com/pytest-dev/pytest-qt/commit/0f74d72711ad6e88f47606e1cb1f9f504a23eb8d) Merge pull request [#245](https://github-redirect.dependabot.com/pytest-dev/pytest-qt/issues/245) from The-Compiler/fix-qinfo
- [`00ce480`](https://github.com/pytest-dev/pytest-qt/commit/00ce4800d9b33b37eb03db6b2566498620f719d6) Fix compatibility with PyQt5 5.11.3
- [`387428c`](https://github.com/pytest-dev/pytest-qt/commit/387428ca22fcce46cbcdefd41f4b4fc69ebbb372) Merge pull request [#244](https://github-redirect.dependabot.com/pytest-dev/pytest-qt/issues/244) from pytest-dev/release-3.2.0
- [`9c757da`](https://github.com/pytest-dev/pytest-qt/commit/9c757da356d632f2406600e8f5ca3faf2eb58d52) Release v3.2.0
- [`3392573`](https://github.com/pytest-dev/pytest-qt/commit/33925736150b1654adcb2d9e2bf88e6b2ff0e6c5) Merge pull request [#242](https://github-redirect.dependabot.com/pytest-dev/pytest-qt/issues/242) from The-Compiler/assert-called
- [`02140ef`](https://github.com/pytest-dev/pytest-qt/commit/02140ef6b7e54a08dc9b7856df69e436df0b4c86) Add CallbackBlocker.assert_called_with()
- [`6194a02`](https://github.com/pytest-dev/pytest-qt/commit/6194a02eb70220f45a3e57df0f43188e54450f11) Merge pull request [#241](https://github-redirect.dependabot.com/pytest-dev/pytest-qt/issues/241) from pytest-dev/release-3.1.0
- Additional commits viewable in [compare view](https://github.com/pytest-dev/pytest-qt/compare/2.1.2...3.2.2)
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](https://app.dependabot.com):
- 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-qt from 2.1.2 to 3.2.2.
Changelog
*Sourced from [pytest-qt's changelog](https://github.com/pytest-dev/pytest-qt/blob/master/CHANGELOG.rst).* > 3.2.2 (2018-12-13) > ------------------ > > - Fix Off-by-one error in ``modeltester`` (`#249`_). Thanks `[**ext-jmmugnes**](https://github.com/ext-jmmugnes)`_ for the PR. > > .. _#249: https://github-redirect.dependabot.com/pytest-dev/pytest-qt/pull/249 > > > 3.2.1 (2018-10-01) > ------------------ > > - Fixed compatibility with PyQt5 5.11.3 > > 3.2.0 (2018-09-26) > ------------------ > > - The ``CallbackBlocker`` returned by ``qtbot.waitCallback()`` now has a new > ``assert_called_with(...)`` convenience method. > > 3.1.0 (2018-09-23) > ------------------ > > - If Qt's model tester implemented in C++ is available (PyQt5 5.11 or newer), > the ``qtmodeltester`` fixture now uses that instead of the Python > implementation. This can be turned off by passing ``force_py=True`` to > ``qtmodeltester.check()``. > > - The Python code used by ``qtmodeltester`` is now based on the latest Qt > modeltester. This also means that the ``data_display_may_return_none`` > attribute for ``qtmodeltester`` isn't used anymore. > > - New ``qtbot.waitCallback()`` method that returns a ``CallbackBlocker``, which > can be used to wait for a callback to be called. > > - ``qtbot.assertNotEmitted`` now has a new ``wait`` parameter which can be used > to make sure asynchronous signals aren't emitted by waiting after the code in > the ``with`` block finished. > > - The ``qt_wait_signal_raising`` option was renamed to ``qt_default_raising``. > The old name continues to work, but is deprecated. > > - The docs still referred to ``SignalTimeoutError`` in some places, despite it > being renamed to ``TimeoutError`` in the 2.1 release. This is now corrected. > > - Improve debugging output when no Qt wrapper was found. > > - When no context is available for warnings on Qt 5, no ``None:None:0`` line is > shown anymore. > > - The ``no_qt_log`` marker is now registered with pytest so ``--strict`` can be > ... (truncated)Commits
- [`83ad838`](https://github.com/pytest-dev/pytest-qt/commit/83ad838be68625ecc33cabaeb23cb776c8de30a9) Update CHANGELOG for 3.2.2 - [`05301c5`](https://github.com/pytest-dev/pytest-qt/commit/05301c58e548ed76cb76b589f6f64b1d1ce9a3fe) Merge pull request [#249](https://github-redirect.dependabot.com/pytest-dev/pytest-qt/issues/249) from ext-jmmugnes/patch-1 - [`6680570`](https://github.com/pytest-dev/pytest-qt/commit/66805707631669add3ea3ead1668b31110128693) fixed bug [#248](https://github-redirect.dependabot.com/pytest-dev/pytest-qt/issues/248) - [`0f74d72`](https://github.com/pytest-dev/pytest-qt/commit/0f74d72711ad6e88f47606e1cb1f9f504a23eb8d) Merge pull request [#245](https://github-redirect.dependabot.com/pytest-dev/pytest-qt/issues/245) from The-Compiler/fix-qinfo - [`00ce480`](https://github.com/pytest-dev/pytest-qt/commit/00ce4800d9b33b37eb03db6b2566498620f719d6) Fix compatibility with PyQt5 5.11.3 - [`387428c`](https://github.com/pytest-dev/pytest-qt/commit/387428ca22fcce46cbcdefd41f4b4fc69ebbb372) Merge pull request [#244](https://github-redirect.dependabot.com/pytest-dev/pytest-qt/issues/244) from pytest-dev/release-3.2.0 - [`9c757da`](https://github.com/pytest-dev/pytest-qt/commit/9c757da356d632f2406600e8f5ca3faf2eb58d52) Release v3.2.0 - [`3392573`](https://github.com/pytest-dev/pytest-qt/commit/33925736150b1654adcb2d9e2bf88e6b2ff0e6c5) Merge pull request [#242](https://github-redirect.dependabot.com/pytest-dev/pytest-qt/issues/242) from The-Compiler/assert-called - [`02140ef`](https://github.com/pytest-dev/pytest-qt/commit/02140ef6b7e54a08dc9b7856df69e436df0b4c86) Add CallbackBlocker.assert_called_with() - [`6194a02`](https://github.com/pytest-dev/pytest-qt/commit/6194a02eb70220f45a3e57df0f43188e54450f11) Merge pull request [#241](https://github-redirect.dependabot.com/pytest-dev/pytest-qt/issues/241) from pytest-dev/release-3.1.0 - Additional commits viewable in [compare view](https://github.com/pytest-dev/pytest-qt/compare/2.1.2...3.2.2)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](https://app.dependabot.com): - 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.