Repository navigation
Release 9.2.0 - #15271
Merged
Merged
Release 9.2.0#15271
Conversation
bluetech
force-pushed
the
release-9.2.0
branch
from
October 27, 2026 20:18
e76890c to
e2cf3bc
Compare
bluetech
reviewed
Oct 27, 2026
| * Aditya | ||
| * Alex Chen | ||
| * Andrew Barnes | ||
| * Anthropic Claude |
Member
There was a problem hiding this comment.
I'm going to remove all of the AI "authors"
| def test_eq_attrs(self): | ||
| import attr | ||
| > import attr | ||
| E ModuleNotFoundError: No module named 'attr' |
Member
There was a problem hiding this comment.
Hmm this is not right, I'll look into it.
Member
There was a problem hiding this comment.
Added a commit to fix this. Not sure it's the best solution but I don't want to block the release to start investigating too much.
| -------------------------------------------- | ||
|
|
||
| - `#14742 <https://github.com/pytest-dev/pytest/issues/14742>`_: The private ``_pytest.python.CallSpec2`` name has been renamed to ``CallSpec``. | ||
| The old ``CallSpec2`` alias remains available for now and will be removed in pytest 10. |
| The old ``CallSpec2`` alias remains available for now and will be removed in pytest 10. | ||
|
|
||
|
|
||
| - `#14755 <https://github.com/pytest-dev/pytest/issues/14755>`_: Schedule *yield_fixture* decorator for removal in pytest 10. |
| class-scoped fixtures, see :issue:`10819` and :issue:`14011`. | ||
|
|
||
|
|
||
| - `#14808 <https://github.com/pytest-dev/pytest/issues/14808>`_: Passing a non-string value to a ``string``-typed ini option now emits a ``pytest.PytestRemovedIn10Warning``. This affects ``[tool.pytest.ini_options]`` in ``pyproject.toml``, where TOML arrays are kept as lists by ``make_scalar`` instead of being converted to strings. In pytest 10 this will raise a ``TypeError``, matching the behavior of the corresponding TOML config path. |
Member
There was a problem hiding this comment.
I'll remove the bit about make_scalar which is an internal detail, not for the changelog
|
|
||
|
|
||
| - `#15153 <https://github.com/pytest-dev/pytest/issues/15153>`_: The :confval:`verbosity_assertions`, :confval:`verbosity_test_cases`, :confval:`verbosity_subtests`, :confval:`tmp_path_retention_count`, :confval:`log_level`, :confval:`log_cli_level`, :confval:`log_file_level` and :confval:`log_auto_indent` configuration options now accept native integer (and, for ``log_auto_indent``, boolean) values in TOML configuration files, while still accepting strings for backward compatibility. | ||
| :confval:`log_file_mode` and :confval:`parametrize_long_str_id_strategy` now report invalid values as a usage error. |
Member
There was a problem hiding this comment.
Removing parametrize_long_str_id_strategy from here since it's added in this release
| - `#14638 <https://github.com/pytest-dev/pytest/issues/14638>`_: Top-level options in ``pytest.toml`` and ``.pytest.toml`` files now raise an error instead of being silently ignored when no ``[pytest]`` table is present. | ||
|
|
||
|
|
||
| - `#14675 <https://github.com/pytest-dev/pytest/issues/14675>`_: The :confval:`truncation_limit_lines` and :confval:`truncation_limit_chars` configuration options now accept integer values in TOML configuration files, while still accepting strings for backward compatibility. |
Member
There was a problem hiding this comment.
Combining this with the other changelog about same bug for other options
| This can happen particularly when many tests are defined in separate classes which inherit from a base class which defines fixtures (the fixtures are repeated per class). | ||
|
|
||
|
|
||
| - `#14953 <https://github.com/pytest-dev/pytest/issues/14953>`_: The :confval:`max_warnings` configuration option now accepts integer values in TOML configuration files, while still accepting strings for backward compatibility. |
| - `#15052 <https://github.com/pytest-dev/pytest/issues/15052>`_: Fixed possible off-by-one line numbers in :option:`--fixtures` and :option:`--fixtures-per-test` output. | ||
|
|
||
|
|
||
| - `#15132 <https://github.com/pytest-dev/pytest/issues/15132>`_: Native TOML numeric values are now accepted for the ``faulthandler_timeout`` |
| Added flaky test papers published on the `Test FLARE <https://test-flare.github.io/>`__ project to the list of flaky papers in ``plugins.rst``. | ||
|
|
||
|
|
||
| - `#14834 <https://github.com/pytest-dev/pytest/issues/14834>`_: Added :pypi:`pytest-skip-slow` to the annotated list of third-party plugins. |
Member
There was a problem hiding this comment.
Removing this as we don't really document such changes
bluetech
force-pushed
the
release-9.2.0
branch
from
October 27, 2026 20:31
e2cf3bc to
0b71654
Compare
bluetech
marked this pull request as ready for review
October 27, 2026 20:32
Member
|
Hmm codespell pre-commit fails us due to:
@SemTiOne I bet you never thought your name will fail a pytest release 😀 (just kidding, I will look at how to work around this) |
bluetech
force-pushed
the
release-9.2.0
branch
from
October 27, 2026 20:42
0b71654 to
ae1d0ff
Compare
bluetech
approved these changes
Oct 27, 2026
This branch was successfully deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Created by the prepare release pr workflow.
Once all builds pass and it has been approved by one or more maintainers, start the deploy workflow, using these parameters:
Use workflow from:release-9.2.0.Release version:9.2.0.Or execute on the command line:
gh workflow run deploy.yml -r release-9.2.0 -f version=9.2.0After the workflow has been approved by a core maintainer, the package will be uploaded to PyPI automatically.