Update dependency pytest-randomly to v4 #1095
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
requested review from
andrecsilva,
clavedeluna and
drdavella
as code owners
renovate
bot
force-pushed
the
renovate/pytest-randomly-4.x
branch
from
0c3fe7a to
6174651
Compare
clavedeluna
approved these changes
Sep 29, 2025
renovate
bot
force-pushed
the
renovate/pytest-randomly-4.x
branch
from
6174651 to
d770f7c
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Note
Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to
mend[bot].This notice will be removed on 2025-10-07.
This PR contains the following updates:
==3.*->==4.*Release Notes
pytest-dev/pytest-randomly (pytest-randomly)
v4.0.1Compare Source
Remove the random state caching, which would grow without bound, leaking memory in long test runs.
The caching was added to slightly speed up re-using the same (final) seed, but since the final seed is now different for each test, it has no effect.
PR #​690 <https://github.com/pytest-dev/pytest-randomly/issues/687>__.Modify Numpy seed restriction, replacing hashing with a modulo operation.
The extra work to hash is unnecessary now that we generate a final seed per test with CRC32.
This change saves ~500ns per test when Numpy is installed.
PR #​691 <https://github.com/pytest-dev/pytest-randomly/issues/691>__.v4.0.0Compare Source
Support Python 3.14.
Use a different random seed per test, based on the test ID.
This change should mean that tests exercise more random data values in a given run, and that any randomly-generated identifiers have a lower chance of collision when stored in a shared resource like a database.
PR #​687 <https://github.com/pytest-dev/pytest-randomly/issues/687>.Thanks to Bryce Drennan for the suggestion in
Issue #​600 <https://github.com/pytest-dev/pytest-randomly/issues/600>and initial implementation inPR #​617 <https://github.com/pytest-dev/pytest-randomly/pull/617>__.Move from MD5 to CRC32 for hashing test IDs, as it’s 5x faster and we don’t need cryptographic security.
Issue #​686 <https://github.com/pytest-dev/pytest-randomly/issues/686>__.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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.