Merged
Conversation
bluetech
approved these changes
Jul 20, 2024
Member
|
(I'm reviewing the change notes, please hold on) |
Member
|
@nicoddemus I already ran the deploy workflow, so I think it's too late for this PR... |
Member
|
Bummer... well I'm almost finished, will publish the suggestions soon |
nicoddemus
reviewed
Jul 20, 2024
|
|
||
| - `#12231 <https://github.com/pytest-dev/pytest/issues/12231>`_: Added `--xfail-tb` flag, which turns on traceback output for XFAIL results. | ||
|
|
||
| * If the `--xfail-tb` flag is not sent, tracebacks for XFAIL results are NOT shown. |
Member
There was a problem hiding this comment.
Suggested change
| * If the `--xfail-tb` flag is not sent, tracebacks for XFAIL results are NOT shown. | |
| * If the `--xfail-tb` flag is not given, tracebacks for XFAIL results are NOT shown. |
| -- by :user:`lovetheguitar` | ||
|
|
||
|
|
||
| - `#12567 <https://github.com/pytest-dev/pytest/issues/12567>`_: Added ``--no-fold-skipped`` command line option |
Member
There was a problem hiding this comment.
Suggested change
| - `#12567 <https://github.com/pytest-dev/pytest/issues/12567>`_: Added ``--no-fold-skipped`` command line option | |
| - `#12567 <https://github.com/pytest-dev/pytest/issues/12567>`_: Added ``--no-fold-skipped`` command line option. |
| - `#12567 <https://github.com/pytest-dev/pytest/issues/12567>`_: Added ``--no-fold-skipped`` command line option | ||
|
|
||
| If this option is set, then skipped tests in short summary are no longer grouped | ||
| by reason but all tests are printed individually with correct nodeid in the same |
Member
There was a problem hiding this comment.
Suggested change
| by reason but all tests are printed individually with correct nodeid in the same | |
| by reason but all tests are printed individually with their nodeid in the same |
Comment on lines
+76
to
+78
| - `#12467 <https://github.com/pytest-dev/pytest/issues/12467>`_: Migrated all internal type-annotations to the python3.10+ style by using the `annotations` future import. | ||
|
|
||
| -- by :user:`RonnyPfannschmidt` |
Member
There was a problem hiding this comment.
I suggest we move this to Contributor-facing changes as it is an internal change.
| -- by :user:`webknjaz`. | ||
|
|
||
|
|
||
| - `#12544 <https://github.com/pytest-dev/pytest/issues/12544>`_, `#12545 <https://github.com/pytest-dev/pytest/issues/12545>`_: The ``_in_venv()`` function now detects Python virtual environments by |
Member
There was a problem hiding this comment.
Suggested change
| - `#12544 <https://github.com/pytest-dev/pytest/issues/12544>`_, `#12545 <https://github.com/pytest-dev/pytest/issues/12545>`_: The ``_in_venv()`` function now detects Python virtual environments by | |
| - `#12544 <https://github.com/pytest-dev/pytest/issues/12544>`_, `#12545 <https://github.com/pytest-dev/pytest/issues/12545>`_: Python virtual environment detection was improved by |
| - `#12275 <https://github.com/pytest-dev/pytest/issues/12275>`_: Fix collection error upon encountering an :mod:`abstract <abc>` class, including abstract `unittest.TestCase` subclasses. | ||
|
|
||
|
|
||
| - `#12328 <https://github.com/pytest-dev/pytest/issues/12328>`_: Fix a regression in pytest 8.0.0 where package-scoped parameterized items were not correctly reordered to minimize setups/teardowns in some cases. |
Member
There was a problem hiding this comment.
Suggested change
| - `#12328 <https://github.com/pytest-dev/pytest/issues/12328>`_: Fix a regression in pytest 8.0.0 where package-scoped parameterized items were not correctly reordered to minimize setups/teardowns in some cases. | |
| - `#12328 <https://github.com/pytest-dev/pytest/issues/12328>`_: Fixed a regression in pytest 8.0.0 where package-scoped parameterized items were not correctly reordered to minimize setups/teardowns in some cases. |
| - `#12328 <https://github.com/pytest-dev/pytest/issues/12328>`_: Fix a regression in pytest 8.0.0 where package-scoped parameterized items were not correctly reordered to minimize setups/teardowns in some cases. | ||
|
|
||
|
|
||
| - `#12424 <https://github.com/pytest-dev/pytest/issues/12424>`_: Fix crash with `assert testcase is not None` assertion failure when re-running unittest tests using plugins like pytest-rerunfailures. Regressed in 8.2.2. |
Member
There was a problem hiding this comment.
Suggested change
| - `#12424 <https://github.com/pytest-dev/pytest/issues/12424>`_: Fix crash with `assert testcase is not None` assertion failure when re-running unittest tests using plugins like pytest-rerunfailures. Regressed in 8.2.2. | |
| - `#12424 <https://github.com/pytest-dev/pytest/issues/12424>`_: Fixed crash with `assert testcase is not None` assertion failure when re-running unittest tests using plugins like pytest-rerunfailures. Regressed in 8.2.2. |
| - `#12472 <https://github.com/pytest-dev/pytest/issues/12472>`_: Fixed a crash when returning category ``"error"`` or ``"failed"`` with a custom test status from :hook:`pytest_report_teststatus` hook -- :user:`pbrezina`. | ||
|
|
||
|
|
||
| - `#12505 <https://github.com/pytest-dev/pytest/issues/12505>`_: Improve handling of invalid regex patterns in :func:`pytest.raises(match=r'...') <pytest.raises>` by providing a clear error message. |
Member
There was a problem hiding this comment.
Suggested change
| - `#12505 <https://github.com/pytest-dev/pytest/issues/12505>`_: Improve handling of invalid regex patterns in :func:`pytest.raises(match=r'...') <pytest.raises>` by providing a clear error message. | |
| - `#12505 <https://github.com/pytest-dev/pytest/issues/12505>`_: Improved handling of invalid regex patterns in :func:`pytest.raises(match=r'...') <pytest.raises>` by providing a clear error message. |
|
|
||
|
|
||
| - `#12577 <https://github.com/pytest-dev/pytest/issues/12577>`_: `CI` and `BUILD_NUMBER` environment variables role is discribed in | ||
| the reference doc. They now also appears when doing `pytest -h` |
Member
There was a problem hiding this comment.
Suggested change
| the reference doc. They now also appears when doing `pytest -h` | |
| the reference doc. They now also appear when doing `pytest -h` |
|
|
||
| - `#11771 <https://github.com/pytest-dev/pytest/issues/11771>`_, `#12557 <https://github.com/pytest-dev/pytest/issues/12557>`_: The PyPy runtime version has been updated to 3.9 from 3.8 that introduced | ||
| a flaky bug at the garbage collector which was not expected to fix there | ||
| as the V3.8 is EoL. |
Member
There was a problem hiding this comment.
Suggested change
| as the V3.8 is EoL. | |
| as the 3.8 is EoL. |
Member
|
@nicoddemus OK please post them, will apply them separately. |
Member
|
Hmm I made a mistake -- the 8.3.0 doesn't contain the release notes! Let me handle it... :) |
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
3 participants
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-8.3.0.Release version:8.3.0.Or execute on the command line:
gh workflow run deploy.yml -r release-8.3.0 -f version=8.3.0After the workflow has been approved by a core maintainer, the package will be uploaded to PyPI automatically.