This repository has been archived by the owner on Jun 14, 2024. It is now read-only.
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:
6.2.0
->6.2.5
Release Notes
pytest-dev/pytest (pytest)
v6.2.5
Compare Source
pytest 6.2.5 (2021-08-29)
Trivial/Internal Changes
pluggy 1.0
or later.v6.2.4
Compare Source
pytest 6.2.4 (2021-05-04)
Bug Fixes
v6.2.3
Compare Source
pytest 6.2.3 (2021-04-03)
Bug Fixes
#8414: pytest used to create directories under
/tmp
with world-readablepermissions. This means that any user in the system was able to read
information written by tests in temporary directories (such as those created by
the
tmp_path
/tmpdir
fixture). Now the directories are created withprivate permissions.
pytest used silenty use a pre-existing
/tmp/pytest-of-<username>
directory,even if owned by another user. This means another user could pre-create such a
directory and gain control of another user's temporary directory. Now such a
condition results in an error.
v6.2.2
Compare Source
pytest 6.2.2 (2021-01-25)
Bug Fixes
faulthandler
plugin for occasions when running withtwisted.logger
and usingpytest --capture=no
.v6.2.1
Compare Source
pytest 6.2.1 (2020-12-15)
Bug Fixes
#7678: Fixed bug where
ImportPathMismatchError
would be raised for files compiled inthe host and loaded later from an UNC mounted path (Windows).
#8132: Fixed regression in
approx
: in 6.2.0approx
no longer raisesTypeError
when dealing with non-numeric types, falling back to normal comparison.Before 6.2.0, array types like tf.DeviceArray fell through to the scalar case,
and happened to compare correctly to a scalar if they had only one element.
After 6.2.0, these types began failing, because they inherited neither from
standard Python number hierarchy nor from
numpy.ndarray
.approx
now converts arguments tonumpy.ndarray
if they expose the arrayprotocol and are not scalars. This treats array-like objects like numpy arrays,
regardless of size.
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 becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.