test_ok2/changelog
Alex Lambson ba32a3bd87
Handle disabled logging in 'caplog.set_level' and 'caplog.at_level' (#8758)
Forces requested `caplog` logging levels to be enabled if they were disabled via `logging.disable()`

`[attr-defined]` mypy error ignored in `logging.py` because there were existing errors with the imports
and `loggin.Logger.manager` is an attr set at runtime. Since it's in the standard lib I can't really fix that.

Ignored an attr-defined error in `src/_pytest/config/__init__.py` because the re-export is necessary.

Fixes #8711
2023-05-18 10:18:59 -03:00
..
8711.improvement.rst Handle disabled logging in 'caplog.set_level' and 'caplog.at_level' (#8758) 2023-05-18 10:18:59 -03:00
10169.bugfix.rst Do not break on very long command-line options 2023-05-12 09:34:15 -03:00
10831.bugfix.rst Fix `pytrace=False` and `--tb=line` reports `None` (#10905) 2023-04-16 20:31:45 +00:00
10901.feature.rst code: add ExceptionInfo.from_exception 2023-04-12 13:16:48 +03:00
10907.improvement.rst doc: add missing changelog for #10907 2023-04-16 18:22:51 +03:00
10940.improvement.rst Improve verbose output by wrapping skip/xfail reasons with margin (#10958) 2023-05-06 12:15:11 -03:00
10987.bugfix.rst Consider testpaths for initial conftests 2023-05-12 09:34:15 -03:00
10999.bugfix.rst monkeypatch: add support for TypedDict (#11000) 2023-05-14 22:17:00 +03:00
11005.improvement.rst Include reason in cache path warnings to aid debugging (#11005) 2023-05-18 10:11:47 -03:00
README.rst docs: use doc/en/_build/html for html output (#6842) 2020-02-29 00:47:30 +01:00
_template.rst Update CHANGELOG template to put issue links at the start of entries 2018-07-07 11:02:33 -03:00

README.rst

This directory contains "newsfragments" which are short files that contain a small **ReST**-formatted
text that will be added to the next ``CHANGELOG``.

The ``CHANGELOG`` will be read by **users**, so this description should be aimed to pytest users
instead of describing internal changes which are only relevant to the developers.

Make sure to use full sentences in the **past or present tense** and use punctuation, examples::

    Improved verbose diff output with sequences.

    Terminal summary statistics now use multiple colors.

Each file should be named like ``<ISSUE>.<TYPE>.rst``, where
``<ISSUE>`` is an issue number, and ``<TYPE>`` is one of:

* ``feature``: new user facing features, like new command-line options and new behavior.
* ``improvement``: improvement of existing functionality, usually without requiring user intervention (for example, new fields being written in ``--junitxml``, improved colors in terminal, etc).
* ``bugfix``: fixes a bug.
* ``doc``: documentation improvement, like rewording an entire session or adding missing docs.
* ``deprecation``: feature deprecation.
* ``breaking``: a change which may break existing suites, such as feature removal or behavior change.
* ``vendor``: changes in packages vendored in pytest.
* ``trivial``: fixing a small typo or internal change that might be noteworthy.

So for example: ``123.feature.rst``, ``456.bugfix.rst``.

If your PR fixes an issue, use that number here. If there is no issue,
then after you submit the PR and get the PR number you can add a
changelog using that instead.

If you are not sure what issue type to use, don't hesitate to ask in your PR.

``towncrier`` preserves multiple paragraphs and formatting (code blocks, lists, and so on), but for entries
other than ``features`` it is usually better to stick to a single paragraph to keep it concise.

You can also run ``tox -e docs`` to build the documentation
with the draft changelog (``doc/en/_build/html/changelog.html``) if you want to get a preview of how your change will look in the final release notes.