Bump pytest-qt from 4.2.0 to 4.4.0

[dependabot]

Bumps pytest-qt from 4.2.0 to 4.4.0.

Changelog

Sourced from pytest-qt's changelog.

4.4.0 (2024-02-07)

• pluggy >=1.1 is now required: we now use new-style hook wrappers, which are less error prone.

• Fixed exception handling so they are properly cleared in Python 3.12, due to the new sys.last_exc <https://docs.python.org/3/library/sys.html#sys.last_exc>__ attribute ([#532](https://github.com/pytest-dev/pytest-qt/issues/532)_).

.. _#532: pytest-dev/pytest-qt#532

4.3.1 (2023-12-22)

• Added official support for Python 3.12.

• Python 3.7 is no longer supported.

• qapp now sets up the QApplication instance with a command line argument like this QApplication([prog_name]) instead of using an empty list QApplication([]). Here prog_name is the name of the app which defaults to pytest-qt-app, but can be redefined in the pytest.ini file, see :ref:qapp fixture<setting-qapp-name>. Alternatively, the arguments that will be passed to QApplication can be defined explicitly using the qapp_args fixture. This means that the default behavior of the qapp_args fixture is now also changed accordingly: it now returns the list [prog_name] instead of an empty list. Thanks to @The-Compiler_ ([#483](https://github.com/pytest-dev/pytest-qt/issues/483)) and @hakonhagland ([#515](https://github.com/pytest-dev/pytest-qt/issues/515)_).

.. _#515: pytest-dev/pytest-qt#515 .. _#483: pytest-dev/pytest-qt#483

4.3.0 (2023-12-22)

• Failure during publish.

Commits

• 172e779 Release 4.4.0
• bd3469b Use new-style hook wrappers (#542)
• 4d099f5 Add me to FUNDING.yml (#540)
• 60bc6c0 [pre-commit.ci] pre-commit autoupdate (#538)
• c1c9e9a [pre-commit.ci] pre-commit autoupdate (#537)
• ed5668a Fix test_exceptions_dont_leak in Python 3.12 (#535)
• 36a436d [pre-commit.ci] pre-commit autoupdate (#536)
• 0b22ccb Merge pull request #534 from nicoddemus/release-4.3.0
• 9a9804d Fix GitHub Release publishing
• 063ada2 Use an environment for deploy
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)