-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update all dependencies #934
Merged
Merged
Conversation
This file contains 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
trusted-contributions-gcf
bot
added
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
owlbot:run
Add this label to trigger the Owlbot post processor.
labels
Feb 7, 2024
product-auto-label
bot
added
size: xs
Pull request size is extra small.
api: bigtable
Issues related to the googleapis/python-bigtable API.
labels
Feb 7, 2024
gcf-owl-bot
bot
removed
the
owlbot:run
Add this label to trigger the Owlbot post processor.
label
Feb 7, 2024
yoshi-kokoro
removed
the
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
label
Feb 7, 2024
renovate-bot
changed the title
chore(deps): update dependency google-cloud-monitoring to v2.19.1
chore(deps): update all dependencies
Feb 8, 2024
renovate-bot
force-pushed
the
renovate/all
branch
from
February 8, 2024 01:39
c2a3c74
to
a3ed60c
Compare
product-auto-label
bot
added
size: s
Pull request size is small.
and removed
size: xs
Pull request size is extra small.
labels
Feb 8, 2024
trusted-contributions-gcf
bot
added
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
owlbot:run
Add this label to trigger the Owlbot post processor.
labels
Feb 8, 2024
gcf-owl-bot
bot
removed
the
owlbot:run
Add this label to trigger the Owlbot post processor.
label
Feb 8, 2024
yoshi-kokoro
removed
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
labels
Feb 8, 2024
renovate-bot
force-pushed
the
renovate/all
branch
from
February 14, 2024 19:33
a3ed60c
to
5029ad9
Compare
trusted-contributions-gcf
bot
added
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
owlbot:run
Add this label to trigger the Owlbot post processor.
labels
Feb 14, 2024
gcf-owl-bot
bot
removed
the
owlbot:run
Add this label to trigger the Owlbot post processor.
label
Feb 14, 2024
yoshi-kokoro
removed
the
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
label
Feb 14, 2024
renovate-bot
force-pushed
the
renovate/all
branch
from
February 16, 2024 22:19
5029ad9
to
618ad37
Compare
trusted-contributions-gcf
bot
added
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
owlbot:run
Add this label to trigger the Owlbot post processor.
labels
Feb 16, 2024
gcf-owl-bot
bot
removed
the
owlbot:run
Add this label to trigger the Owlbot post processor.
label
Feb 16, 2024
yoshi-kokoro
removed
the
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
label
Feb 16, 2024
renovate-bot
force-pushed
the
renovate/all
branch
from
February 23, 2024 00:58
618ad37
to
ecf6ca7
Compare
renovate-bot
force-pushed
the
renovate/all
branch
from
July 22, 2024 23:17
edfcbd3
to
8a9c20c
Compare
trusted-contributions-gcf
bot
added
the
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
label
Jul 22, 2024
yoshi-kokoro
removed
the
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
label
Jul 22, 2024
renovate-bot
force-pushed
the
renovate/all
branch
from
July 25, 2024 14:06
8a9c20c
to
2a8a5bf
Compare
trusted-contributions-gcf
bot
added
the
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
label
Jul 25, 2024
yoshi-kokoro
removed
the
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
label
Jul 25, 2024
renovate-bot
force-pushed
the
renovate/all
branch
from
July 30, 2024 23:40
2a8a5bf
to
51135b7
Compare
trusted-contributions-gcf
bot
added
the
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
label
Jul 30, 2024
yoshi-kokoro
removed
the
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
label
Jul 30, 2024
renovate-bot
force-pushed
the
renovate/all
branch
from
August 6, 2024 01:46
51135b7
to
6bd3e91
Compare
trusted-contributions-gcf
bot
added
the
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
label
Aug 6, 2024
yoshi-kokoro
removed
the
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
label
Aug 6, 2024
daniel-sanche
added
kokoro:run
Add this label to force Kokoro to re-run the tests.
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
labels
Aug 12, 2024
yoshi-kokoro
removed
kokoro:run
Add this label to force Kokoro to re-run the tests.
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
labels
Aug 12, 2024
daniel-sanche
added
owlbot:run
Add this label to trigger the Owlbot post processor.
and removed
owlbot:run
Add this label to trigger the Owlbot post processor.
labels
Aug 12, 2024
gcf-owl-bot
bot
removed
the
owlbot:run
Add this label to trigger the Owlbot post processor.
label
Aug 12, 2024
trusted-contributions-gcf
bot
added
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
owlbot:run
Add this label to trigger the Owlbot post processor.
labels
Aug 12, 2024
gcf-owl-bot
bot
removed
the
owlbot:run
Add this label to trigger the Owlbot post processor.
label
Aug 12, 2024
yoshi-kokoro
removed
the
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
label
Aug 12, 2024
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
daniel-sanche
added
the
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
label
Sep 25, 2024
yoshi-kokoro
removed
the
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
label
Sep 25, 2024
daniel-sanche
approved these changes
Sep 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
api: bigtable
Issues related to the googleapis/python-bigtable API.
size: m
Pull request size is medium.
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.54.0
->==2.58.0
==3.2.3
->==3.5.0
==3.13.1
->==3.15.4
==2.22.0
->==2.25.0
==2.23.0
->==2.25.0
==2.19.0
->==2.22.2
v2.1.0
->v2.1.1
==2024.3.2
->==2024.4.15
==24.0
->==24.1
==4.2.0
->==4.2.2
==7.4.4
->==8.3.2
22.04
->24.04
==20.25.1
->==20.26.3
Release Notes
kislyuk/argcomplete (argcomplete)
v3.5.0
Compare Source
===============================
Use project.scripts instead of setuptools scripts (#498)
Test infrastructure improvements
v3.4.0
Compare Source
===============================
No stdin for python calls from bash completion functions (#488)
Prevents usage of stdin by (python) executables that are called
during completion generation. This prevents the completion locking up
the entire shell when the python script is broken i.e. it enters an
interactive mode (REPL) instead of generating the completions, as
expected.
Localize shell variable REPLY to avoid overwriting users’ value
(#489)
The variable REPLY is used by default by the
read
shell builtinto store the return value, and like all bash/zsh variables, is scoped
globally. This change allows this variable to be used for other needs
by appropriately scoping its internal use by an argcomplete utility
function that uses
read
.v3.3.0
Compare Source
===============================
update is required to use argcomplete on Python 3.11.9+ or 3.12.3+.
tox-dev/py-filelock (filelock)
v3.15.4
Compare Source
What's Changed
file_lock
as positional argument by @kwist-sgr in https://github.com/tox-dev/filelock/pull/347Full Changelog: tox-dev/filelock@3.15.3...3.15.4
v3.15.3
Compare Source
What's Changed
TypeError: _CountedFileLock.__init__() got an unexpected keyword argument 'timeout'
by @kwist-sgr in https://github.com/tox-dev/filelock/pull/345Full Changelog: tox-dev/filelock@3.15.2...3.15.3
v3.15.2
Compare Source
What's Changed
New Contributors
Full Changelog: tox-dev/filelock@3.15.1...3.15.2
v3.15.1
Compare Source
What's Changed
Full Changelog: tox-dev/filelock@3.15.0...3.15.1
v3.15.0
Compare Source
What's Changed
New Contributors
Full Changelog: tox-dev/filelock@3.14.0...3.15.0
v3.14.0
Compare Source
What's Changed
blocking
parameter on lock constructor with tests and docs by @iamkhav in https://github.com/tox-dev/filelock/pull/325New Contributors
Full Changelog: tox-dev/filelock@3.13.4...3.14.0
v3.13.4
Compare Source
What's Changed
Full Changelog: tox-dev/filelock@3.13.3...3.13.4
v3.13.3
Compare Source
What's Changed
Full Changelog: tox-dev/filelock@3.13.2...3.13.3
v3.13.2
Compare Source
What's Changed
/tmp
by @kota-iizuka in https://github.com/tox-dev/filelock/pull/317New Contributors
Full Changelog: tox-dev/filelock@3.13.1...3.13.2
googleapis/python-bigtable (google-cloud-bigtable)
v2.25.0
Compare Source
Features
Bug Fixes
v2.24.0
Compare Source
Features
Bug Fixes
v2.23.1
Compare Source
Bug Fixes
v2.23.0
Compare Source
Features
Bug Fixes
ValueError
intest__validate_universe_domain
(#929) (aa76a5a)googleapis/google-cloud-python (google-cloud-monitoring)
v2.22.2
: google-cloud-monitoring: v2.22.2Compare Source
Bug Fixes
v2.22.1
: google-cloud-monitoring: v2.22.1Compare Source
Bug Fixes
v2.22.0
: google-cloud-monitoring: v2.22.0Compare Source
Features
v2.21.0
: google-cloud-monitoring: v2.21.0Compare Source
Features
Documentation
v2.20.0
: google-cloud-secret-manager: v2.20.0Compare Source
Features
Documentation
v2.19.4
: google-cloud-monitoring: v2.19.4Compare Source
Documentation
v2.19.3
: google-cloud-monitoring: v2.19.3Compare Source
Bug Fixes
v2.19.2
: google-cloud-monitoring: v2.19.2Compare Source
Bug Fixes
google-api-core>=1.34.1
(#12307) (be87bc4)mock
(#12317) (1988e0d)v2.19.1
: google-cloud-monitoring: v2.19.1Compare Source
Bug Fixes
google-github-actions/setup-gcloud (google-github-actions/setup-gcloud)
v2.1.1
Compare Source
What's Changed
New Contributors
Full Changelog: google-github-actions/setup-gcloud@v2.1.0...v2.1.1
wntrblm/nox (nox)
v2024.4.15
Compare Source
pypa/packaging (packaging)
v24.1
Compare Source
What's Changed
_parser
docstring by @pradyunsg in https://github.com/pypa/packaging/pull/784markers.default_environment()
by @edgarrmondragon in https://github.com/pypa/packaging/pull/753New Contributors
Full Changelog: pypa/packaging@24.0...24.1
platformdirs/platformdirs (platformdirs)
v4.2.2
Compare Source
What's Changed
New Contributors
Full Changelog: tox-dev/platformdirs@4.2.1...4.2.2
v4.2.1
Compare Source
What's Changed
New Contributors
Full Changelog: tox-dev/platformdirs@4.2.0...4.2.1
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
v8.2.2
Compare Source
pytest 8.2.2 (2024-06-04)
Bug Fixes
.pytest_cache
) creation. Regressed in pytest 8.2.0.Improved Documentation
lack of thread safety in pytest as a possible source of flakyness.
v8.2.1
Compare Source
pytest 8.2.1 (2024-05-19)
Improvements
Bug Fixes
.pytest_cache
directories becamerwx------
instead of the expectedrwxr-xr-x
.Trivial/Internal Changes
v8.2.0
Compare Source
pytest 8.2.0 (2024-04-27)
Deprecations
#12069: A deprecation warning is now raised when implementations of one of the following hooks request a deprecated
py.path.local
parameter instead of thepathlib.Path
parameter which replaced it:pytest_ignore_collect
{.interpreted-text role="hook"} - thepath
parameter - usecollection_path
instead.pytest_collect_file
{.interpreted-text role="hook"} - thepath
parameter - usefile_path
instead.pytest_pycollect_makemodule
{.interpreted-text role="hook"} - thepath
parameter - usemodule_path
instead.pytest_report_header
{.interpreted-text role="hook"} - thestartdir
parameter - usestart_path
instead.pytest_report_collectionfinish
{.interpreted-text role="hook"} - thestartdir
parameter - usestart_path
instead.The replacement parameters are available since pytest 7.0.0.
The old parameters will be removed in pytest 9.0.0.
See
legacy-path-hooks-deprecated
{.interpreted-text role="ref"} for more details.Features
#11871: Added support for reading command line arguments from a file using the prefix character
@
, like e.g.:pytest @​tests.txt
. The file must have one argument per line.See
Read arguments from file <args-from-file>
{.interpreted-text role="ref"} for details.Improvements
#11523:
pytest.importorskip
{.interpreted-text role="func"} will now issue a warning if the module could be found, but raisedImportError
{.interpreted-text role="class"} instead ofModuleNotFoundError
{.interpreted-text role="class"}.The warning can be suppressed by passing
exc_type=ImportError
topytest.importorskip
{.interpreted-text role="func"}.See
import-or-skip-import-error
{.interpreted-text role="ref"} for details.#11728: For
unittest
-based tests, exceptions during class cleanup (as raised by functions registered withTestCase.addClassCleanup <unittest.TestCase.addClassCleanup>
{.interpreted-text role="meth"}) are now reported instead of silently failing.#11777: Text is no longer truncated in the
short test summary info
section when-vv
is given.#12112: Improved namespace packages detection when
consider_namespace_packages
{.interpreted-text role="confval"} is enabled, covering more situations (like editable installs).#9502: Added
PYTEST_VERSION
{.interpreted-text role="envvar"} environment variable which is defined at the start of the pytest session and undefined afterwards. It contains the value ofpytest.__version__
, and among other things can be used to easily check if code is running from within a pytest run.Bug Fixes
#12065: Fixed a regression in pytest 8.0.0 where test classes containing
setup_method
and tests using@staticmethod
or@classmethod
would crash withAttributeError: 'NoneType' object has no attribute 'setup_method'
.Now the
request.instance <pytest.FixtureRequest.instance>
{.interpreted-text role="attr"} attribute of tests using@staticmethod
and@classmethod
is no longerNone
, but a fresh instance of the class, like in non-static methods.Previously it was
None
, and all fixtures of such tests would share a singleself
.#12135: Fixed issue where fixtures adding their finalizer multiple times to fixtures they request would cause unreliable and non-intuitive teardown ordering in some instances.
#12194: Fixed a bug with
--importmode=importlib
and--doctest-modules
where child modules did not appear as attributes in parent modules.#1489: Fixed some instances where teardown of higher-scoped fixtures was not happening in the reverse order they were initialized in.
Trivial/Internal Changes
pluggy>=1.5.0
is now required.cache <cache>
{.interpreted-text role="ref"}: create supporting files (CACHEDIR.TAG
,.gitignore
, etc.) in a temporary directory to provide atomic semantics.v8.1.2
Compare Source
pytest 8.1.2 (2024-04-26)
Bug Fixes
pytest.approx
{.interpreted-text role="func"} when used with [numpy]{.title-ref} arrays and comparing with other types.v8.1.1
Compare Source
pytest 8.1.1 (2024-03-08)
::: {.note}
::: {.title}
Note
:::
This release is not a usual bug fix release -- it contains features and improvements, being a follow up
to
8.1.0
, which has been yanked from PyPI.:::
Features
#11475: Added the new
consider_namespace_packages
{.interpreted-text role="confval"} configuration option, defaulting toFalse
.If set to
True
, pytest will attempt to identify modules that are part of namespace packages when importing modules.#11653: Added the new
verbosity_test_cases
{.interpreted-text role="confval"} configuration option for fine-grained control of test execution verbosity.See
Fine-grained verbosity <pytest.fine_grained_verbosity>
{.interpreted-text role="ref"} for more details.Improvements
#10865:
pytest.warns
{.interpreted-text role="func"} now validates thatwarnings.warn
{.interpreted-text role="func"} was called with a [str]{.title-ref} or a [Warning]{.title-ref}.Currently in Python it is possible to use other types, however this causes an exception when
warnings.filterwarnings
{.interpreted-text role="func"} is used to filter those warnings (see CPython #103577 for a discussion).While this can be considered a bug in CPython, we decided to put guards in pytest as the error message produced without this check in place is confusing.
#11311: When using
--override-ini
for paths in invocations without a configuration file defined, the current working directory is usedas the relative directory.
Previoulsy this would raise an
AssertionError
{.interpreted-text role="class"}.#11475:
--import-mode=importlib <import-mode-importlib>
{.interpreted-text role="ref"} now tries to import modules using the standard import mechanism (but still without changing :pysys.path
{.interpreted-text role="data"}), falling back to importing modules directly only if that fails.This means that installed packages will be imported under their canonical name if possible first, for example
app.core.models
, instead of having the module name always be derived from their path (for example.env310.lib.site_packages.app.core.models
).#11801: Added the
iter_parents() <_pytest.nodes.Node.iter_parents>
{.interpreted-text role="func"} helper method on nodes.It is similar to
listchain <_pytest.nodes.Node.listchain>
{.interpreted-text role="func"}, but goes from bottom to top, and returns an iterator, not a list.#11850: Added support for
sys.last_exc
{.interpreted-text role="data"} for post-mortem debugging on Python>=3.12.#11962: In case no other suitable candidates for configuration file are found, a
pyproject.toml
(even without a[tool.pytest.ini_options]
table) will be considered as the configuration file and define therootdir
.#11978: Add
--log-file-mode
option to the logging plugin, enabling appending to log-files. This option accepts either"w"
or"a"
and defaults to"w"
.Previously, the mode was hard-coded to be
"w"
which truncates the file before logging.#12047: When multiple finalizers of a fixture raise an exception, now all exceptions are reported as an exception group.
Previously, only the first exception was reported.
Bug Fixes
#11475: Fixed regression where
--importmode=importlib
would import non-test modules more than once.#11904: Fixed a regression in pytest 8.0.0 that would cause test collection to fail due to permission errors when using
--pyargs
.This change improves the collection tree for tests specified using
--pyargs
, see12043
{.interpreted-text role="pull"} for a comparison with pytest 8.0 and <8.#12011: Fixed a regression in 8.0.1 whereby
setup_module
xunit-style fixtures are not executed when--doctest-modules
is passed.#12014: Fix the
stacklevel
used when warning about marks used on fixtures.#12039: Fixed a regression in
8.0.2
where tests created usingtmp_path
{.interpreted-text role="fixture"} have been collected multiple times in CI under Windows.Improved Documentation
tmp_path
fixture in more detail.Trivial/Internal Changes
#11785: Some changes were made to private functions which may affect plugins which access them:
FixtureManager._getautousenames()
now takes aNode
itself instead of the nodeid.FixtureManager.getfixturedefs()
now takes theNode
itself instead of the nodeid._pytest.nodes.iterparentnodeids()
function is removed without replacement.Prefer to traverse the node hierarchy itself instead.
If you really need to, copy the function from the previous pytest release.
#12069: Delayed the deprecation of the following features to
9.0.0
:node-ctor-fspath-deprecation
{.interpreted-text role="ref"}.legacy-path-hooks-deprecated
{.interpreted-text role="ref"}.It was discovered after
8.1.0
was released that the warnings about the impeding removal were not being displayed, so the team decided to revert the removal.This is the reason for
8.1.0
being yanked.pytest 8.1.0 (YANKED)
::: {.note}
::: {.title}
Note
:::
This release has been yanked: it broke some plugins without the proper warning period, due to
some warnings not showing up as expected.
See #12069.
:::
v8.1.0
Compare Source
pytest 8.1.0 (YANKED)
Features
#11475: Added the new
consider_namespace_packages
{.interpreted-text role="confval"} configuration option, defaulting toFalse
.If set to
True
, pytest will attempt to identify modules that are part of namespace packages when importing modules.#11653: Added the new
verbosity_test_cases
{.interpreted-text role="confval"} configuration option for fine-grained control of test execution verbosity.See
Fine-grained verbosity <pytest.fine_grained_verbosity>
{.interpreted-text role="ref"} for more details.Improvements
#10865:
pytest.warns
{.interpreted-text role="func"} now validates thatwarnings.warn
{.interpreted-text role="func"} was called with a [str]{.title-ref} or a [Warning]{.title-ref}.Currently in Python it is possible to use other types, however this causes an exception when
warnings.filterwarnings
{.interpreted-text role="func"} is used to filter those warnings (see CPython #103577 for a discussion).While this can be considered a bug in CPython, we decided to put guards in pytest as the error message produced without this check in place is confusing.
#11311: When using
--override-ini
for paths in invocations without a configuration file defined, the current working directory is usedas the relative directory.
Previoulsy this would raise an
AssertionError
{.interpreted-text role="class"}.#11475:
--import-mode=importlib <import-mode-importlib>
{.interpreted-text role="ref"} now tries to import modules using the standard import mechanism (but still without changing :pysys.path
{.interpreted-text role="data"}), falling back to importing modules directly only if that fails.This means that installed packages will be imported under their canonical name if possible first, for example
app.core.models
, instead of having the module name always be derived from their path (for example.env310.lib.site_packages.app.core.models
).#11801: Added the
iter_parents() <_pytest.nodes.Node.iter_parents>
{.interpreted-text role="func"} helper method on nodes.It is similar to
listchain <_pytest.nodes.Node.listchain>
{.interpreted-text role="func"}, but goes from bottom to top, and returns an iterator, not a list.#11850: Added support for
sys.last_exc
{.interpreted-text role="data"} for post-mortem debugging on Python>=3.12.#11962: In case no other suitable candidates for configuration file are found, a
pyproject.toml
(even without a[tool.pytest.ini_options]
table) will be considered as the configuration file and define therootdir
.#11978: Add
--log-file-mode
option to the logging plugin, enabling appending to log-files. This option accepts either"w"
or"a"
and defaults to"w"
.Previously, the mode was hard-coded to be
"w"
which truncates the file before logging.#12047: When multiple finalizers of a fixture raise an exception, now all exceptions are reported as an exception group.
Previously, only the first exception was reported.
Bug Fixes
#11904: Fixed a regression in pytest 8.0.0 that would cause test collection to fail due to permission errors when using
--pyargs
.This change improves the collection tree for tests specified using
--pyargs
, see12043
{.interpreted-text role="pull"} for a comparison with pytest 8.0 and <8.#12011: Fixed a regression in 8.0.1 whereby
setup_module
xunit-style fixtures are not executed when--doctest-modules
is passed.#12014: Fix the
stacklevel
used when warning about marks used on fixtures.#12039: Fixed a regression in
8.0.2
where tests created usingtmp_path
{.interpreted-text role="fixture"} have been collected multiple times in CI under Windows.Improved Documentation
tmp_path
fixture in more detail.Trivial/Internal Changes
FixtureManager._getautousenames()
now takes aNode
itself instead of the nodeid.FixtureManager.getfixturedefs()
now takes theNode
itself instead of the nodeid._pytest.nodes.iterparentnodeids()
function is removed without replacement.Prefer to traverse the node hierarchy itself instead.
If you really need to, copy the function from the previous pytest release.
v8.0.2
Compare Source
pytest 8.0.2 (2024-02-24)
Bug Fixes
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.
👻 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.