chore(deps): update python-nonmajor #348
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==2.0.31
->==2.0.32
==3.10.2
->==3.10.3
==2.32.0
->==2.33.0
==4.25.3
->==4.25.4
==8.2.2
->==8.3.2
==0.23.7
->==0.23.8
Release Notes
aio-libs/aiohttp (aiohttp)
v3.10.3
: 3.10.3Compare Source
Bug fixes
Fixed multipart reading when stream buffer splits the boundary over several read() calls -- by :user:
Dreamsorcerer
.Related issues and pull requests on GitHub:
#8653.
Fixed :py:class:
aiohttp.TCPConnector
doing blocking I/O in the event loop to create theSSLContext
-- by :user:bdraco
.The blocking I/O would only happen once per verify mode. However, it could cause the event loop to block for a long time if the
SSLContext
creation is slow, which is more likely during startup when the disk cache is not yet present.Related issues and pull requests on GitHub:
#8672.
Miscellaneous internal changes
Improved performance of :py:meth:
~aiohttp.ClientWebSocketResponse.receive
and :py:meth:~aiohttp.web.WebSocketResponse.receive
when there is no timeout. -- by :user:bdraco
.The timeout context manager is now avoided when there is no timeout as it accounted for up to 50% of the time spent in the :py:meth:
~aiohttp.ClientWebSocketResponse.receive
and :py:meth:~aiohttp.web.WebSocketResponse.receive
methods.Related issues and pull requests on GitHub:
#8660.
Improved performance of starting request handlers with Python 3.12+ -- by :user:
bdraco
.Related issues and pull requests on GitHub:
#8661.
Improved performance of HTTP keep-alive checks -- by :user:
bdraco
.Previously, when processing a request for a keep-alive connection, the keep-alive check would happen every second; the check is now rescheduled if it fires too early instead.
Related issues and pull requests on GitHub:
#8662.
Improved performance of generating random WebSocket mask -- by :user:
bdraco
.Related issues and pull requests on GitHub:
#8667.
googleapis/google-auth-library-python (google-auth)
v2.33.0
Compare Source
Features
StaticCredentials
using access tokens (#1559) (dc17dfc)Bug Fixes
Documentation
pytest-dev/pytest (pytest)
v8.3.2
Compare Source
pytest 8.3.2 (2024-07-24)
Bug fixes
#12652: Resolve regression [conda]{.title-ref} environments where no longer being automatically detected.
-- by
RonnyPfannschmidt
{.interpreted-text role="user"}v8.3.1
Compare Source
pytest 8.3.1 (2024-07-20)
The 8.3.0 release failed to include the change notes and docs for the release. This patch release remedies this. There are no other changes.
v8.3.0
Compare Source
pytest-dev/pytest-asyncio (pytest-asyncio)
v0.23.8
: pytest-asyncio 0.23.8Compare Source
0.23.8 (2024-07-17)
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.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.