Bump the dev-dependencies group with 2 updates

[dependabot]

Updates the requirements on pvi and pytest-asyncio to permit the latest version.
Updates pvi to 0.8

Release notes

Sourced from pvi's releases.

0.8

Breaking changes since 0.7.X

• SignalR.pv -> SignalR.read_pv
• SignalW.pv -> SignalW.write_pv
• CheckBox -> ToggleButton except in rows and tables
• Remove prefix arg from Formatter.format and include literal macros in Signals
• Index buttons changed so that row label is device name and button label is macros. Previously they were both device name, but this is not unique when multiple instances of a device are created. It is now recommended to include row labels for Groups with DeviceRef buttons to be able to see the two distinct labels.

What's Changed

• Refactor Pydantic models with TypedModel by @​GDYendell in epics-containers/pvi#88
• Update to include macros in device yaml by @​GDYendell in epics-containers/pvi#89
• Update PVI template generation by @​GDYendell in epics-containers/pvi#92
• Fix SignalRW read_pv convert by @​GDYendell in epics-containers/pvi#93
• Implement missing widgets by @​evalott100 in epics-containers/pvi#83
• Add ToggleButton widget to replace CheckBox for binary records by @​GDYendell in epics-containers/pvi#81
• Fix regex for parsing records by @​gilesknap in epics-containers/pvi#100
• Improvements made while integrating latest pvi with ibek by @​GDYendell in epics-containers/pvi#104

Full Changelog: epics-containers/pvi@0.7.2...0.8

Changelog

Sourced from pvi's changelog.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog <https://keepachangelog.com/en/1.0.0/>, and this project adheres to Semantic Versioning <https://semver.org/spec/v2.0.0.html>.

Unreleased <../../compare/0.1...HEAD>_

Nothing yet

0.1 <../../releases/tag/0.1>_ - 2021-12-22

Initial release

Commits

• 50cb1be Merge pull request #104 from epics-containers/ibek-dev
• 62d5410 Update IndexEntry to use label as given
• a560f8b Improve convert logic
• 5c14b6e Merge pull request #100 from epics-containers/pv-macros2
• c68696e Fix regex for parsing records
• 0702019 Merge pull request #81 from epics-containers/toggle-widget
• ecf0c82 Update AsynBinary to verify ZNAM and ONAM are set in convert
• 8c08731 Move classes around to allow AsynParameter to have AsynRecords
• 780ff99 Add ToggleButton widget and use for binary records
• e1d5556 Merge pull request #83 from epics-containers/implement_missing_widgets
• Additional commits viewable in compare view

Updates pytest-asyncio from 0.21.1 to 0.23.6

Release notes

Sourced from pytest-asyncio's releases.

pytest-asyncio 0.23.6

0.23.6 (2024-03-19)

• Fix compatibility with pytest 8.2 #800

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

pytest-asyncio 0.23.5.post1

0.23.5 (2024-02-09)

• Declare compatibility with pytest 8 #737
• Fix typing errors with recent versions of mypy #769
• Prevent DeprecationWarning about internal use of asyncio.get_event_loop() from affecting test cases #757

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

pytest-asyncio 0.23.5

0.23.5 (2024-02-09)

• Declare compatibility with pytest 8 #737
• Fix typing errors with recent versions of mypy #769
• Prevent DeprecationWarning about internal use of asyncio.get_event_loop() from affecting test cases #757

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

pytest-asyncio 0.23.5a0

0.23.5 (UNRELEASED)

• Declare compatibility with pytest 8 #737
• Fix typing errors with recent versions of mypy #769

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

pytest-asyncio 0.23.4

0.23.4 (2024-01-28)

• pytest-asyncio no longer imports additional, unrelated packages during test collection #729
• Addresses further issues that caused an internal pytest error during test collection
• Declares incompatibility with pytest 8 #737

pytest-asyncio 0.23.4a2

0.23.4 (UNRELEASED)

• pytest-asyncio no longer imports additional, unrelated packages during test collection #729
• Addresses further issues that caused an internal pytest error during test collection

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

... (truncated)

Commits

• c34da04 [docs] Mentioned pytest 8.2 compatibility fix in changelog.
• 143f745 Fix compatibility with pytest 8.2 FixtureDef.unittest removal
• 13d4b79 Remove unused function _removesuffix
• cdd2c49 Use FixtureRequest instead of SubRequest
• c3429fa Build(deps): Bump packaging from 23.2 to 24.0 in /dependencies/docs
• 5f2338d Build(deps): Bump pypa/gh-action-pypi-publish from 1.8.12 to 1.8.14
• 726c6e0 Build(deps): Bump coverage from 7.4.3 to 7.4.4 in /dependencies/default
• 8bd8288 Build(deps): Bump pytest from 8.0.2 to 8.1.1 in /dependencies/default
• ef3b347 Build(deps): Bump packaging from 23.2 to 24.0 in /dependencies/default
• b22d84e [docs] Fixes the example showing how to run all tests in a session-scoped loop.
• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Superseded by #106.