Bump the pip-minor-patch group with 14 updates

[dependabot]

Bumps the pip-minor-patch group with 14 updates:

Package	From	To
uvicorn	0.27.1	0.29.0
sentry-sdk	1.40.4	1.45.0
httpx	0.26.0	0.27.0
email-validator	2.1.0.post1	2.1.1
redis	5.0.1	5.0.3
black	24.2.0	24.3.0
wemake-python-styleguide	0.18.0	0.19.2
mypy	1.8.0	1.9.0
coverage	7.4.1	7.4.4
pytest-asyncio	0.23.5	0.23.6
pytest-mock	3.12.0	3.14.0
aiosqlite	0.19.0	0.20.0
rich	13.7.0	13.7.1
ruff	0.2.1	0.3.5

Updates uvicorn from 0.27.1 to 0.29.0

Release notes

Sourced from uvicorn's releases.

Version 0.29.0

Added

• Cooperative signal handling by @​maxfischer2781 in encode/uvicorn#1600

---

Full Changelog: encode/uvicorn@0.28.1...0.29.0

Version 0.28.1

Fixed

• Revert raise ClientDisconnected on HTTP (#2276)

---

Full Changelog: encode/uvicorn@0.28.0...0.28.1

Version 0.28.0

Added

• Raise ClientDisconnected on send() when client disconnected (#2220) 12/02/24

Fixed

• Except AttributeError on sys.stdin.fileno() for Windows IIS10 (#1947) 29/02/24
• Use X-Forwarded-Proto for WebSockets scheme when the proxy provides it (#2258) 01/03/24

---

Full Changelog: encode/uvicorn@0.27.1...0.28.0

Changelog

Sourced from uvicorn's changelog.

0.29.0 - 2024-03-19

Added

• Cooperative signal handling (#1600) 19/03/24

0.28.1 - 2024-03-19

Fixed

• Revert raise ClientDisconnected on HTTP (#2276) 19/03/24

0.28.0 - 2024-03-09

Added

• Raise ClientDisconnected on send() when client disconnected (#2220) 12/02/24

Fixed

• Except AttributeError on sys.stdin.fileno() for Windows IIS10 (#1947) 29/02/24
• Use X-Forwarded-Proto for WebSockets scheme when the proxy provides it (#2258) 01/03/24

Commits

• fe85206 Version 0.29.0 (#2279)
• 9e32e8e Cooperative signal handling (#1600)
• f73b8be Version 0.28.1 (#2277)
• 76a3812 Revert raise ClientDisconnected on HTTP (#2276) (#2276)
• a05ae64 Version 0.28.0 (#2269)
• 4a503d8 Change ruff rules (#2251)
• 0d4747e Use X-Forwarded-Proto for WebSockets scheme when the proxy provides it (#2258)
• 93897b5 Except AttributeError on sys.stdin.fileno() for Windows IIS10 (#1947)
• ed2d655 Bump cryptography from 42.0.2 to 42.0.4 (#2253)
• 1e5f1be Raise ClientDisconnected on send() when client disconnected (#2220)
• See full diff in compare view

Updates sentry-sdk from 1.40.4 to 1.45.0

Release notes

Sourced from sentry-sdk's releases.

1.45.0

This is the final 1.x release for the forseeable future. Development will continue on the 2.x release line. The first 2.x version will be available in the next few weeks.

Various fixes & improvements

• Allow to upsert monitors (#2929) by @​sentrivana

  It's now possible to provide monitor_config to the monitor decorator/context manager directly:

  from sentry_sdk.crons import monitor
  All keys except schedule are optional
  monitor_config = {
  "schedule": {"type": "crontab", "value": "0 0 * * *"},
  "timezone": "Europe/Vienna",
  "checkin_margin": 10,
  "max_runtime": 10,
  "failure_issue_threshold": 5,
  "recovery_threshold": 5,
  }
  @​monitor(monitor_slug='<monitor-slug>', monitor_config=monitor_config)
  def tell_the_world():
  print('My scheduled task...')

  Check out the cron docs for details.

• Add Django signals_denylist to filter signals that are attached to by signals_spans (#2758) by @​lieryan

  If you want to exclude some Django signals from performance tracking, you can use the new signals_denylist Django option:

  import django.db.models.signals
  import sentry_sdk
  sentry_sdk.init(
  ...
  integrations=[
  DjangoIntegration(
  ...
  signals_denylist=[
  django.db.models.signals.pre_init,
  django.db.models.signals.post_init,
  ],
  ),
  ],
  )

... (truncated)

Changelog

Sourced from sentry-sdk's changelog.

1.45.0

This is the final 1.x release for the forseeable future. Development will continue on the 2.x release line. The first 2.x version will be available in the next few weeks.

Various fixes & improvements

• Allow to upsert monitors (#2929) by @​sentrivana

  It's now possible to provide monitor_config to the monitor decorator/context manager directly:

  from sentry_sdk.crons import monitor
  All keys except schedule are optional
  monitor_config = {
  "schedule": {"type": "crontab", "value": "0 0 * * *"},
  "timezone": "Europe/Vienna",
  "checkin_margin": 10,
  "max_runtime": 10,
  "failure_issue_threshold": 5,
  "recovery_threshold": 5,
  }
  @​monitor(monitor_slug='<monitor-slug>', monitor_config=monitor_config)
  def tell_the_world():
  print('My scheduled task...')

  Check out the cron docs for details.

• Add Django signals_denylist to filter signals that are attached to by signals_spans (#2758) by @​lieryan

  If you want to exclude some Django signals from performance tracking, you can use the new signals_denylist Django option:

  import django.db.models.signals
  import sentry_sdk
  sentry_sdk.init(
  ...
  integrations=[
  DjangoIntegration(
  ...
  signals_denylist=[
  django.db.models.signals.pre_init,
  django.db.models.signals.post_init,
  ],
  ),
  ],
  )

... (truncated)

Commits

• 51a906c Update CHANGELOG.md
• 7570e39 release: 1.45.0
• e22abb6 fix(metrics): Change data_category from statsd to metric_bucket (#2954)
• fab65e6 feat(metrics): New normalization of keys, values, units (#2946)
• a584653 feat(typing): Make monitor_config a TypedDict (#2931)
• a1ab339 feat(metrics): Add value, unit to before_emit_metric (#2958)
• 18ccb8f chore: Remove experimental metric summary options (#2957)
• a422dd7 fix(profiler): Accessing mro might throw a ValueError (#2952)
• 11e1f9a feat(integrations): Add django signals_denylist to filter signals that are at...
• f5ec34c build(deps): bump types-protobuf from 4.24.0.20240311 to 4.24.0.20240408 (#2941)
• Additional commits viewable in compare view

Updates httpx from 0.26.0 to 0.27.0

Release notes

Sourced from httpx's releases.

Version 0.27.0

0.27.0 (21st February, 2024)

Deprecated

• The app=... shortcut has been deprecated. Use the explicit style of transport=httpx.WSGITransport() or transport=httpx.ASGITransport() instead.

Fixed

• Respect the http1 argument while configuring proxy transports. (#3023)
• Fix RFC 2069 mode digest authentication. (#3045)

Changelog

Sourced from httpx's changelog.

0.27.0 (21st February, 2024)

Deprecated

• The app=... shortcut has been deprecated. Use the explicit style of transport=httpx.WSGITransport() or transport=httpx.ASGITransport() instead.

Fixed

• Respect the http1 argument while configuring proxy transports. (#3023)
• Fix RFC 2069 mode digest authentication. (#3045)

Commits

• 326b943 Version 0.27.0 (#3095)
• 3faa4a8 Improve 'Custom transports' docs (#3081)
• c51af4b Extensions docs (#3080)
• cabd1c0 Deprecate app=... in favor of explicit WSGITransport/ASGITransport. (#3...
• 6f46152 Bump the python-packages group with 6 updates (#3077)
• 37a2901 Mention NO_PROXY environment variable on Advanced Usage page (#3066)
• 371b6e9 Use __future__.annotations (#3068)
• 4f6edf3 test parse_header_links via public api (#3061)
• c7cd6aa test obfuscate_sensitive_headers via public api (#3063)
• 15f9253 Drop outdated section (#3057)
• Additional commits viewable in compare view

Updates email-validator from 2.1.0.post1 to 2.1.1

Release notes

Sourced from email-validator's releases.

v2.1.1 (February 26, 2024)

• Fixed typo 'marking' instead of 'marketing' in case-insensitive mailbox name list.
• When DNS-based deliverability checks fail, in some cases exceptions are now thrown with raise ... from for better nested exception tracking.
• Fixed tests to work when no local resolver can be configured.
• This project is now licensed under the Unlicense (instead of CC0).
• Minor improvements to tests.
• Minor improvements to code style.

Changelog

Sourced from email-validator's changelog.

2.1.1 (February 26, 2024)

• Fixed typo 'marking' instead of 'marketing' in case-insensitive mailbox name list.
• When DNS-based deliverability checks fail, in some cases exceptions are now thrown with raise ... from for better nested exception tracking.
• Fixed tests to work when no local resolver can be configured.
• This project is now licensed under the Unlicense (instead of CC0).
• Minor improvements to tests.
• Minor improvements to code style.

2.1.0 (October 22, 2023)

• Python 3.8+ is now required (support for Python 3.7 was dropped).
• The old email field on the returned ValidatedEmail object, which in the previous version was superseded by normalized, will now raise a deprecation warning if used. See https://stackoverflow.com/q/879173 for strategies to suppress the DeprecationWarning.
• A __version__ module attribute is added.
• The email address argument to validate_email is now marked as positional-only to better reflect the documented usage using the new Python 3.8 feature.

2.0.0 (April 15, 2023)

This is a major update to the library, but since email address specs haven't changed there should be no significant changes to which email addresses are considered valid or invalid with default options. There are new options for accepting unusual email addresses that were previously always rejected, some changes to how DNS errors are handled, many changes in error message text, and major internal improvements including the addition of type annotations. Python 3.7+ is now required. Details follow:

• Python 2.x and 3.x versions through 3.6, and dnspython 1.x, are no longer supported. Python 3.7+ with dnspython 2.x are now required.
• The dnspython package is no longer required if DNS checks are not used, although it will install automatically.
• NoNameservers and NXDOMAIN DNS errors are now handled differently: NoNameservers no longer fails validation, and NXDOMAIN now skips checking for an A/AAAA fallback and goes straight to failing validation.
• Some syntax error messages have changed because they are now checked explicitly rather than as a part of other checks.
• The quoted-string local part syntax (e.g. multiple @-signs, spaces, etc. if surrounded by quotes) and domain-literal addresses (e.g. @[192.XXX...] or @[IPv6:...]) are now parsed but not considered valid by default. Better error messages are now given for these addresses since it can be confusing for a technically valid address to be rejected, and new allow_quoted_local and allow_domain_literal options are added to allow these addresses if you really need them.
• Some other error messages have changed to not repeat the email address in the error message.
• The email field on the returned ValidatedEmail object has been renamed to normalized to be clearer about its importance, but access via .email is also still supported.
• Some mailbox names like postmaster are now normalized to lowercase per RFC 2142.
• The library has been reorganized internally into smaller modules.
• The tests have been reorganized and expanded. Deliverability tests now mostly use captured DNS responses so they can be run off-line.
• The main tool now reads options to validate_email from environment variables.
• Type annotations have been added to the exported methods and the ValidatedEmail class and some internal methods.
• The old dict-like pattern for the return value of validate_email is deprecated.

Versions 2.0.0.post1 and 2.0.0.post2 corrected some packaging issues. 2.0.0.post2 also added a check for an invalid combination of arguments.

Version 1.3.1 (January 21, 2023)

• The new SPF 'v=spf1 -all' (reject-all) deliverability check is removed in most cases. It now is performed only for domains that do not have MX records but do have an A/AAAA fallback record.

Version 1.3.0 (September 18, 2022)

• Deliverability checks now check for 'v=spf1 -all' SPF records as a way to reject more bad domains.
• Special use domain names now raise EmailSyntaxError instead of EmailUndeliverableError since they are performed even if check_deliverability is off.
• New module-level attributes are added to override the default values of the keyword arguments and the special-use domains list.

... (truncated)

Commits

• See full diff in compare view

Updates redis from 5.0.1 to 5.0.3

Release notes

Sourced from redis's releases.

5.0.3

Changes

🐛 Bug Fixes

• Fix breaking change: message in LockError is now optional (#3176)

🧰 Maintenance

• Bump release-drafter/release-drafter from 5 to 6 (#3171)
• Bump rojopolis/spellcheck-github-actions from 0.35.0 to 0.36.0 (#3172)
• Remove redundant async-timeout dependency (#3177)

5.0.2

Changes

🚀 New Features

• Allow to control the minimum SSL version (#3127)
• Add modules support to async RedisCluster (#3115)
• Adding lock_name to LockError (#3023)
• Add GEOSHAPE field type for index creation of RediSearch (#2957)

🐛 Bug Fixes

• Fix retry logic for pubsub and pipeline (#3134)
• Ignore TypeError on disconnect (within multiprocess) (#3149)
• Release already acquired connections on ClusterPipeline, when get_connection raises an exception (#3133)
• Fix possible pipeline connections leak (#3104)
• Return a copy of the response from cache (#3106)
• Fix: HSET unexpectedly mutates the list passed to items (#3103)
• Fix acl_genpass with bits (#3062)
• Allow the parsing of the asking command to forward original options (#3012)
• Fix parsing of FT.PROFILE result (#3063)
• Use disable_decoding in async read_response with hiredis parser. (#3042)
• Fix return types in json commands (#3071)
• Fix Specifying Target Nodes broken hyperlink (#3072)

🧰 Maintenance

• Fix incorrect asserts in test and ensure connections are closed (#3004)
• Revert stale issue version update (#3142)
• Docs: Add timeout parameter for get_message example (#3129)
• Bump codecov/codecov-action from 3 to 4 (#3131)
• Bump actions/stale from 3 to 9 (#3132)
• Fix grammer in BlockingConnectionPool class documentation (#3120)
• Updating async-timeout to 4.0.3 (#3109)
• Fix type hint of arbitrary argument lists (#2908)
• Fix JSON.OBJLEN type hint (#2966)
• Fix HDEL type hint (#3029)
• Docs: organize cluster mode part of lua scripting (#3073)

... (truncated)

Commits

• 1784b37 Version 5.0.3 (#3179)
• e90b7c5 Cherry pick for v5.0.3 (#3178)
• 535f90e Version 5.0.2 (#3164)
• 911aa37 Cherry pick for v5.0.2 (#3159)
• See full diff in compare view

Updates black from 24.2.0 to 24.3.0

Release notes

Sourced from black's releases.

24.3.0

Highlights

This release is a milestone: it fixes Black's first CVE security vulnerability. If you run Black on untrusted input, or if you habitually put thousands of leading tab characters in your docstrings, you are strongly encouraged to upgrade immediately to fix CVE-2024-21503.

This release also fixes a bug in Black's AST safety check that allowed Black to make incorrect changes to certain f-strings that are valid in Python 3.12 and higher.

Stable style

• Don't move comments along with delimiters, which could cause crashes (#4248)
• Strengthen AST safety check to catch more unsafe changes to strings. Previous versions of Black would incorrectly format the contents of certain unusual f-strings containing nested strings with the same quote type. Now, Black will crash on such strings until support for the new f-string syntax is implemented. (#4270)
• Fix a bug where line-ranges exceeding the last code line would not work as expected (#4273)

Performance

• Fix catastrophic performance on docstrings that contain large numbers of leading tab characters. This fixes CVE-2024-21503. (#4278)

Documentation

• Note what happens when --check is used with --quiet (#4236)

Changelog

Sourced from black's changelog.

24.3.0

Highlights

This release is a milestone: it fixes Black's first CVE security vulnerability. If you run Black on untrusted input, or if you habitually put thousands of leading tab characters in your docstrings, you are strongly encouraged to upgrade immediately to fix CVE-2024-21503.

This release also fixes a bug in Black's AST safety check that allowed Black to make incorrect changes to certain f-strings that are valid in Python 3.12 and higher.

Stable style

• Don't move comments along with delimiters, which could cause crashes (#4248)
• Strengthen AST safety check to catch more unsafe changes to strings. Previous versions of Black would incorrectly format the contents of certain unusual f-strings containing nested strings with the same quote type. Now, Black will crash on such strings until support for the new f-string syntax is implemented. (#4270)
• Fix a bug where line-ranges exceeding the last code line would not work as expected (#4273)

Performance

• Fix catastrophic performance on docstrings that contain large numbers of leading tab characters. This fixes CVE-2024-21503. (#4278)

Documentation

• Note what happens when --check is used with --quiet (#4236)

Commits

• 552baf8 Prepare release 24.3.0 (#4279)
• f000936 Fix catastrophic performance in lines_with_leading_tabs_expanded() (#4278)
• 7b5a657 Fix --line-ranges behavior when ranges are at EOF (#4273)
• 1abcffc Use regex where we ignore case on windows (#4252)
• 719e674 Fix 4227: Improve documentation for --quiet --check (#4236)
• e5510af update plugin url for Thonny (#4259)
• 6af7d11 Fix AST safety check false negative (#4270)
• f03ee11 Ensure blib2to3.pygram is initialized before use (#4224)
• e4bfedb fix: Don't move comments while splitting delimiters (#4248)
• d0287e1 Make trailing comma logic more concise (#4202)
• Additional commits viewable in compare view

Updates wemake-python-styleguide from 0.18.0 to 0.19.2

Release notes

Sourced from wemake-python-styleguide's releases.

Version 0.19.2

Bugfixes

• Fixes WrongEmptyLinesCountViolation crash on Callable[..., ...] #2899

Version 0.19.1

This release fixes how ... is used. For example, it is common to define function stubs / protocols like this:

def some_function(): ...

Now, ... will be excluded from several rules.

Bugfixes

• Fixes TooDeepNestingViolation not to trigger on ... in functions and classes
• Fixes StatementHasNoEffectViolation not to trigger on ... in functions and classes, when it is the only node

Version 0.19.0

This minor version will be the last release with all the flake8 plugins. In the future this project will be migrated to be used together with ruff.

Features

• Adds official python3.12 support
• Breaking: drops python3.8 support
• Breaking: Reconsider object required base class exception: since class Klass[_Type] must not contain object, this rule is change to be the opposite: object explicit base class must not be used. You can use ruff to change all object-based types to the new style: ruff check --select=UP004 --fix . https://docs.astral.sh/ruff/rules/useless-object-inheritance/
• Breaking: allow positional-only parameters, since it is required by mypy when using Concatenate
• Adds support for naming rules for PEP695 type params
• Due to how f-string are parsed in python3.12 several token-based violations are not reported anymore for them: WrongMultilineStringViolation, ImplicitRawStringViolation, WrongUnicodeEscapeViolation, RawStringNotNeededViolation
• wemake output formatter now respects NO_COLOR=1 option to disable text highlighting. See https://no-color.org
• Adds ImportObjectCollisionViolation to detect the same objects imported under different aliases
• Adds reveal_locals to the list of forbidden functions
• Updates flake8 to 7.x

... (truncated)

Changelog

Sourced from wemake-python-styleguide's changelog.

0.19.2

Bugfixes

• Fixes WrongEmptyLinesCountViolation crash on Callable[..., ...] #2899

0.19.1

This release fixes how ... is used. For example, it is common to define function stubs / protocols like this:

def some_function(): ...

Now, ... will be excluded from several rules.

Bugfixes

• Fixes TooDeepNestingViolation not to trigger on ... in functions and classes
• Fixes StatementHasNoEffectViolation not to trigger on ... in functions and classes, when it is the only node

0.19.0

This minor version will be the last release with all the flake8 plugins. In the future this project will be migrated to be used together with ruff.

Features

• Adds official python3.12 support
• Breaking: drops python3.8 support
• Breaking: Reconsider object required base class exception: since class Klass[_Type] must not contain object, this rule is change to be the opposite: object explicit base class must not be used. You can use ruff to change all object-based types to the new style: ruff check --select=UP004 --fix . https://docs.astral.sh/ruff/rules/useless-object-inheritance/
• Breaking: allow positional-only parameters, since it is required by mypy when using Concatenate
• Adds support for naming rules for PEP695 type params
• Due to how f-string are parsed in python3.12 several token-based violations are not reported anymore for them: WrongMultilineStringViolation, ImplicitRawStringViolation, WrongUnicodeEscapeViolation, RawStringNotNeededViolation
• wemake output formatter now respects NO_COLOR=1 option

... (truncated)

Commits

• 18276e6 Version 0.19.2 (#2900)
• 99ba44e Version 0.19.1 release
• 8670471 Do not report WPS440 when ... is the only node in the function defition (...
• bdecb89 Fix WPS220 for top-level Ellipsis (#2897)
• 3e0565b Improve tests of pep695 (#2895)
• 55d110b Version 0.19.0 release
• 30a0e79 Update flake8
• bb8a278 Support naming validation for PEP695 (#2894)
• 884be48 Fix pattern matching and block overlaps (#2893)
• 3cf1b69 Support MatchStar naming (#2892)
• Additional commits viewable in compare view

Updates mypy from 1.8.0 to 1.9.0

Changelog

Sourced from mypy's changelog.

Mypy Release Notes

Mypy 1.9

We’ve just uploaded mypy 1.9 to the Python Package Index (PyPI). Mypy is a static type checker for Python. This release includes new features, performance improvements and bug fixes. You can install it as follows:

python3 -m pip install -U mypy

You can read the full documentation for this release on Read the Docs.

Breaking Changes

Because the version of typeshed we use in mypy 1.9 doesn't support 3.7, neither does mypy 1.9. (Jared Hance, PR 16883)

We are planning to enable local partial types (enabled via the --local-partial-types flag) later this year by default. This change was announced years ago, but now it's finally happening. This is a major backward-incompatible change, so we'll probably include it as part of the upcoming mypy 2.0 release. This makes daemon and non-daemon mypy runs have the same behavior by default.

Local partial types can also be enabled in the mypy config file:

local_partial_types = True

We are looking at providing a tool to make it easier to migrate projects to use --local-partial-types, but it's not yet clear whether this is practical. The migration usually involves adding some explicit type annotations to module-level and class-level variables.

Basic Support for Type Parameter Defaults (PEP 696)

This release contains new experimental support for type parameter defaults (PEP 696). Please try it out! This feature was contributed by Marc Mueller.

Since this feature will be officially introduced in the next Python feature release (3.13), you will need to import TypeVar, ParamSpec or TypeVarTuple from typing_extensions to use defaults for now.

This example adapted from the PEP defines a default for BotT:

from typing import Generic
from typing_extensions import TypeVar
class Bot: ...
BotT = TypeVar("BotT", bound=Bot, default=Bot)
</tr></table>

... (truncated)

Commits

• 5ff46f8 Remove +dev.
• 155909a [Release 1.9] Unsupport targetting 3.7. (#16883) (#16900)
• 6615cab [Release 1.9] Stubtest: ignore a new protocol dunder (#16895) (#16899)
• b956e6a stubtest: Private parameters can be omitted (#16507)
• ede0b20 Bump ruff to 0.2.0 (#16870)
• 7bdd61f stubgen: Fix crash on star unpack of TypeVarTuple (#16869)
• 8c2ef9d Update hashes in sync-typeshed.py following recent typeshed sync
• 0dd4b6f Revert use of ParamSpec for functools.wraps
• dd12a2d Revert typeshed ctypes change
• d132999 Revert sum literal integer change (#13961)
• Additional commits viewable in compare view

Updates coverage from 7.4.1 to 7.4.4

Changelog

Sourced from coverage's changelog.

Version 7.4.4 — 2024-03-14

• Fix: in some cases, even with [run] relative_files=True, a data file could be created with absolute path names. When combined with other relative data files, it was random whether the absolute file names would be made relative or not. If they weren't, then a file would be listed twice in reports, as detailed in issue 1752_. This is now fixed: absolute file names are always made relative when combining. Thanks to Bruno Rodrigues dos Santos for support.

• Fix: the last case of a match/case statement had an incorrect message if the branch was missed. It said the pattern never matched, when actually the branch is missed if the last case always matched.

• Fix: clicking a line number in the HTML report now positions more accurately.

• Fix: the report:format setting was defined as a boolean, but should be a string. Thanks, Tanaydin Sirin <pull 1754_>_. It is also now documented on the :ref:configuration page <config_report_format>.

.. _issue 1752: nedbat/coveragepy#1752 .. _pull 1754: nedbat/coveragepy#1754

.. _changes_7-4-3:

Version 7.4.3 — 2024-02-23

• Fix: in some cases, coverage could fail with a RuntimeError: "Set changed size during iteration." This is now fixed, closing issue 1733_.

.. _issue 1733: nedbat/coveragepy#1733

.. _changes_7-4-2:

Version 7.4.2 — 2024-02-20

• Fix: setting COVERAGE_CORE=sysmon no longer errors on 3.11 and lower, thanks Hugo van Kemenade <pull 1747_>_. It now issues a warning that sys.monitoring is not available and falls back to the default core instead.

.. _pull 1747: nedbat/coveragepy#1747

.. _changes_7-4-1:

Commits

• bc5e2d7 docs: sample HTML for 7.4.4
• 9b0008b docs: prep for 7.4.4
• a536161 docs: thanks, Bruno Rodrigues dos Santos
• e06e4f9 chore: make doc_upgrade
• f30818e chore: make upgrade
• 1b19799 fix: ensure absolute paths are relative when combined #1752
• 1ef020d build: more cheats for convenient URLs
• 3d57a07 docs: document the report:format setting
• 8e30221 fix: correct the type of report:format in config.py (#1754)
• 6289be8 refactor: use dataclasses, no namedtuple
• Additional commits viewable in compare view

Updates pytest-asyncio from 0.23.5 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.

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

Updates pytest-mock from 3.12.0 to 3.14.0

Release notes

Sourced from pytest-mock's releases.

v3.14.0

• #415: MockType and AsyncMockType can be imported from pytest_mock for type annotation purposes.
• #420: Fixed a regression which would cause mocker.patch.object to not being properly cleared between tests.

v3.13.0

• #417: spy now has spy_return_list, which is a list containing all the values returned by the spied function.
• pytest-mock now requires pytest>=6.2.5.
• #410: pytest-mock's setup.py file is removed. If you relied on this file, e.g. to install pytest using setup.py install, please see Why you shouldn't invoke setup.py directly for alternatives.

Changelog

Sourced from pytest-mock's changelog.

3.14.0 (2024-03-21)

• [#415](https://github.com/pytest-dev/pytest-mock/issues/415) <https://github.com/pytest-dev/pytest-mock/pull/415>_: MockType and AsyncMockType can be imported from pytest_mock for type annotation purposes.

• [#420](https://github.com/pytest-dev/pytest-mock/issues/420) <https://github.com/pytest-dev/pytest-mock/issues/420>_: Fixed a regression which would cause mocker.patch.object to not being properly cleared between tests.

3.13.0 (2024-03-21)

• [#417](https://github.com/pytest-dev/pytest-mock/issues/417) <https://github.com/pytest-dev/pytest-mock/pull/417>_: spy now has spy_return_list, which is a list containing all the values returned by the spied function.
• pytest-mock now requires pytest>=6.2.5.
• [#410](https://github.com/pytest-dev/pytest-mock/issues/410) <https://github.com/pytest-dev/pytest-mock/pull/410>: pytest-mock's setup.py file is removed. If you relied on this file, e.g. to install pytest using setup.py install, please see Why you shouldn't invoke setup.py directly <https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html#summary> for alternatives.

Commits

• 8733134 Update CHANGELOG for 3.14.0
• 5257e3c Refactor MockCache to have a narrow interface
• 4faf92a Fix regression with mocker.patch not being undone correctly
• 6bd8712 Drop pre-Python 3.8 support code
• 366966b Export MockType/AsyncMockType for type annotations (#415)
• 852116b Merge pull request #418 from pytest-dev/release-3.13.0
• ef9461b Add instructions on how to start deploy from command-line
• 5b9d285 Release 3.13.0
• 6d5d6dc Implement spy_return_list (#417)
• dc28a0e [pre-commit.ci] pre-commit autoupdate (#416)
• Additional commits viewable in compare view

Updates aiosqlite from 0.19.0 to 0.20.0

Changelog

Sourced from aiosqlite's changelog.

v0.20.0

Feature release

• Connection .close() method is now idempotent (#238)
• Performance improvements in connection thread and event loop (#213,

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.