Scheduled weekly dependency update for week 13 by pyup-bot · Pull Request #228 · ammesonb/logical-backup

pyup-bot · 2025-03-31T14:01:53Z

Update pytest from 8.2.1 to 8.3.5.

Changelog

8.3.3

=========================

Bug fixes
---------

- `12446 &lt;https://github.com/pytest-dev/pytest/issues/12446&gt;`_: Avoid calling ``property`` (and other instance descriptors) during fixture discovery -- by :user:`asottile`


- `12659 &lt;https://github.com/pytest-dev/pytest/issues/12659&gt;`_: Fixed the issue of not displaying assertion failure differences when using the parameter ``--import-mode=importlib`` in pytest&gt;=8.1.


- `12667 &lt;https://github.com/pytest-dev/pytest/issues/12667&gt;`_: Fixed a regression where type change in `ExceptionInfo.errisinstance` caused `mypy` to fail.


- `12744 &lt;https://github.com/pytest-dev/pytest/issues/12744&gt;`_: Fixed typing compatibility with Python 3.9 or less -- replaced `typing.Self` with `typing_extensions.Self` -- by :user:`Avasam`


- `12745 &lt;https://github.com/pytest-dev/pytest/issues/12745&gt;`_: Fixed an issue with backslashes being incorrectly converted in nodeid paths on Windows, ensuring consistent path handling across environments.


- `6682 &lt;https://github.com/pytest-dev/pytest/issues/6682&gt;`_: Fixed bug where the verbosity levels where not being respected when printing the &quot;msg&quot; part of failed assertion (as in ``assert condition, msg``).


- `9422 &lt;https://github.com/pytest-dev/pytest/issues/9422&gt;`_: Fix bug where disabling the terminal plugin via ``-p no:terminal`` would cause crashes related to missing the ``verbose`` option.

-- by :user:`GTowers1`



Improved documentation
----------------------

- `12663 &lt;https://github.com/pytest-dev/pytest/issues/12663&gt;`_: Clarify that the `pytest_deselected` hook should be called from `pytest_collection_modifyitems` hook implementations when items are deselected.


- `12678 &lt;https://github.com/pytest-dev/pytest/issues/12678&gt;`_: Remove erroneous quotes from `tmp_path_retention_policy` example in docs.



Miscellaneous internal changes
------------------------------

- `12769 &lt;https://github.com/pytest-dev/pytest/issues/12769&gt;`_: Fix typos discovered by codespell and add codespell to pre-commit hooks.

8.3.2

=========================

Bug fixes
---------

- `12652 &lt;https://github.com/pytest-dev/pytest/issues/12652&gt;`_: Resolve regression `conda` environments where no longer being automatically detected.

-- by :user:`RonnyPfannschmidt`

8.3.1

=========================

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.

8.3.0

=========================

New features
------------

- `12231 &lt;https://github.com/pytest-dev/pytest/issues/12231&gt;`_: Added `--xfail-tb` flag, which turns on traceback output for XFAIL results.

* If the `--xfail-tb` flag is not given, tracebacks for XFAIL results are NOT shown.
* The style of traceback for XFAIL is set with `--tb`, and can be `auto|long|short|line|native|no`.
* Note: Even if you have `--xfail-tb` set, you won&#x27;t see them if `--tb=no`.

Some history:

With pytest 8.0, `-rx` or `-ra` would not only turn on summary reports for xfail, but also report the tracebacks for xfail results. This caused issues with some projects that utilize xfail, but don&#x27;t want to see all of the xfail tracebacks.

This change detaches xfail tracebacks from `-rx`, and now we turn on xfail tracebacks with `--xfail-tb`. With this, the default `-rx`/ `-ra` behavior is identical to pre-8.0 with respect to xfail tracebacks. While this is a behavior change, it brings default behavior back to pre-8.0.0 behavior, which ultimately was considered the better course of action.

-- by :user:`okken`


- `12281 &lt;https://github.com/pytest-dev/pytest/issues/12281&gt;`_: Added support for keyword matching in marker expressions.

Now tests can be selected by marker keyword arguments.
Supported values are :class:`int`, (unescaped) :class:`str`, :class:`bool` &amp; :data:`None`.

See :ref:`marker examples &lt;marker_keyword_expression_example&gt;` for more information.

-- by :user:`lovetheguitar`


- `12567 &lt;https://github.com/pytest-dev/pytest/issues/12567&gt;`_: 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 their nodeid in the same
way as other statuses.

-- by :user:`pbrezina`



Improvements in existing functionality
--------------------------------------

- `12469 &lt;https://github.com/pytest-dev/pytest/issues/12469&gt;`_: The console output now uses the &quot;third-party plugins&quot; terminology,
replacing the previously established but confusing and outdated
reference to :std:doc:`setuptools &lt;setuptools:index&gt;`
-- by :user:`webknjaz`.


- `12544 &lt;https://github.com/pytest-dev/pytest/issues/12544&gt;`_, `#12545 &lt;https://github.com/pytest-dev/pytest/issues/12545&gt;`_: Python virtual environment detection was improved by
checking for a :file:`pyvenv.cfg` file, ensuring reliable detection on
various platforms -- by :user:`zachsnickers`.


- `2871 &lt;https://github.com/pytest-dev/pytest/issues/2871&gt;`_: Do not truncate arguments to functions in output when running with `-vvv`.


- `389 &lt;https://github.com/pytest-dev/pytest/issues/389&gt;`_: The readability of assertion introspection of bound methods has been enhanced
-- by :user:`farbodahm`, :user:`webknjaz`, :user:`obestwalter`, :user:`flub`
and :user:`glyphack`.

Earlier, it was like:

.. code-block:: console

   =================================== FAILURES ===================================
   _____________________________________ test _____________________________________

       def test():
   &gt;       assert Help().fun() == 2
   E       assert 1 == 2
   E        +  where 1 = &lt;bound method Help.fun of &lt;example.Help instance at 0x256a830&gt;&gt;()
   E        +    where &lt;bound method Help.fun of &lt;example.Help instance at 0x256a830&gt;&gt; = &lt;example.Help instance at 0x256a830&gt;.fun
   E        +      where &lt;example.Help instance at 0x256a830&gt; = Help()

   example.py:7: AssertionError
   =========================== 1 failed in 0.03 seconds ===========================


And now it&#x27;s like:

.. code-block:: console

   =================================== FAILURES ===================================
   _____________________________________ test _____________________________________

       def test():
   &gt;       assert Help().fun() == 2
   E       assert 1 == 2
   E        +  where 1 = fun()
   E        +    where fun = &lt;test_local.Help object at 0x1074be230&gt;.fun
   E        +      where &lt;test_local.Help object at 0x1074be230&gt; = Help()

   test_local.py:13: AssertionError
   =========================== 1 failed in 0.03 seconds ===========================


- `7662 &lt;https://github.com/pytest-dev/pytest/issues/7662&gt;`_: Added timezone information to the testsuite timestamp in the JUnit XML report.



Bug fixes
---------

- `11706 &lt;https://github.com/pytest-dev/pytest/issues/11706&gt;`_: Fixed reporting of teardown errors in higher-scoped fixtures when using `--maxfail` or `--stepwise`.

Originally added in pytest 8.0.0, but reverted in 8.0.2 due to a regression in pytest-xdist.
This regression was fixed in pytest-xdist 3.6.1.


- `11797 &lt;https://github.com/pytest-dev/pytest/issues/11797&gt;`_: :func:`pytest.approx` now correctly handles :class:`Sequence &lt;collections.abc.Sequence&gt;`-like objects.


- `12204 &lt;https://github.com/pytest-dev/pytest/issues/12204&gt;`_, `#12264 &lt;https://github.com/pytest-dev/pytest/issues/12264&gt;`_: Fixed a regression in pytest 8.0 where tracebacks get longer and longer when multiple
tests fail due to a shared higher-scope fixture which raised -- by :user:`bluetech`.

Also fixed a similar regression in pytest 5.4 for collectors which raise during setup.

The fix necessitated internal changes which may affect some plugins:

* ``FixtureDef.cached_result[2]`` is now a tuple ``(exc, tb)``
 instead of ``exc``.
* ``SetupState.stack`` failures are now a tuple ``(exc, tb)``
 instead of ``exc``.


- `12275 &lt;https://github.com/pytest-dev/pytest/issues/12275&gt;`_: Fixed collection error upon encountering an :mod:`abstract &lt;abc&gt;` class, including abstract `unittest.TestCase` subclasses.


- `12328 &lt;https://github.com/pytest-dev/pytest/issues/12328&gt;`_: Fixed a regression in pytest 8.0.0 where package-scoped parameterized items were not correctly reordered to minimize setups/teardowns in some cases.


- `12424 &lt;https://github.com/pytest-dev/pytest/issues/12424&gt;`_: 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 &lt;https://github.com/pytest-dev/pytest/issues/12472&gt;`_: Fixed a crash when returning category ``&quot;error&quot;`` or ``&quot;failed&quot;`` with a custom test status from :hook:`pytest_report_teststatus` hook -- :user:`pbrezina`.


- `12505 &lt;https://github.com/pytest-dev/pytest/issues/12505&gt;`_: Improved handling of invalid regex patterns in :func:`pytest.raises(match=r&#x27;...&#x27;) &lt;pytest.raises&gt;` by providing a clear error message.


- `12580 &lt;https://github.com/pytest-dev/pytest/issues/12580&gt;`_: Fixed a crash when using the cache class on Windows and the cache directory was created concurrently.


- `6962 &lt;https://github.com/pytest-dev/pytest/issues/6962&gt;`_: Parametrization parameters are now compared using `==` instead of `is` (`is` is still used as a fallback if the parameter does not support `==`).
This fixes use of parameters such as lists, which have a different `id` but compare equal, causing fixtures to be re-computed instead of being cached.


- `7166 &lt;https://github.com/pytest-dev/pytest/issues/7166&gt;`_: Fixed progress percentages (the ``[ 87%]`` at the edge of the screen) sometimes not aligning correctly when running with pytest-xdist ``-n``.



Improved documentation
----------------------

- `12153 &lt;https://github.com/pytest-dev/pytest/issues/12153&gt;`_: Documented using :envvar:`PYTEST_VERSION` to detect if code is running from within a pytest run.


- `12469 &lt;https://github.com/pytest-dev/pytest/issues/12469&gt;`_: The external plugin mentions in the documentation now avoid mentioning
:std:doc:`setuptools entry-points &lt;setuptools:index&gt;` as the concept is
much more generic nowadays. Instead, the terminology of &quot;external&quot;,
&quot;installed&quot;, or &quot;third-party&quot; plugins (or packages) replaces that.

-- by :user:`webknjaz`


- `12577 &lt;https://github.com/pytest-dev/pytest/issues/12577&gt;`_: `CI` and `BUILD_NUMBER` environment variables role is described in
the reference doc. They now also appear when doing `pytest -h`
-- by :user:`MarcBresson`.



Contributor-facing changes
--------------------------

- `12467 &lt;https://github.com/pytest-dev/pytest/issues/12467&gt;`_: Migrated all internal type-annotations to the python3.10+ style by using the `annotations` future import.

-- by :user:`RonnyPfannschmidt`


- `11771 &lt;https://github.com/pytest-dev/pytest/issues/11771&gt;`_, `#12557 &lt;https://github.com/pytest-dev/pytest/issues/12557&gt;`_: 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 3.8 is EoL.

-- by :user:`x612skm`


- `12493 &lt;https://github.com/pytest-dev/pytest/issues/12493&gt;`_: The change log draft preview integration has been refactored to use a
third party extension ``sphinxcontib-towncrier``. The previous in-repo
script was putting the change log preview file at
:file:`doc/en/_changelog_towncrier_draft.rst`. Said file is no longer
ignored in Git and might show up among untracked files in the
development environments of the contributors. To address that, the
contributors can run the following command that will clean it up:

.. code-block:: console

  $ git clean -x -i -- doc/en/_changelog_towncrier_draft.rst

-- by :user:`webknjaz`


- `12498 &lt;https://github.com/pytest-dev/pytest/issues/12498&gt;`_: All the undocumented ``tox`` environments now have descriptions.
They can be listed in one&#x27;s development environment by invoking
``tox -av`` in a terminal.

-- by :user:`webknjaz`


- `12501 &lt;https://github.com/pytest-dev/pytest/issues/12501&gt;`_: The changelog configuration has been updated to introduce more accurate
audience-tailored categories. Previously, there was a ``trivial``
change log fragment type with an unclear and broad meaning. It was
removed and we now have ``contrib``, ``misc`` and ``packaging`` in
place of it.

The new change note types target the readers who are downstream
packagers and project contributors. Additionally, the miscellaneous
section is kept for unspecified updates that do not fit anywhere else.

-- by :user:`webknjaz`


- `12502 &lt;https://github.com/pytest-dev/pytest/issues/12502&gt;`_: The UX of the GitHub automation making pull requests to update the
plugin list has been updated. Previously, the maintainers had to close
the automatically created pull requests and re-open them to trigger the
CI runs. From now on, they only need to click the `Ready for review`
button instead.

-- by :user:`webknjaz`


- `12522 &lt;https://github.com/pytest-dev/pytest/issues/12522&gt;`_: The ``:pull:`` RST role has been replaced with a shorter
``:pr:`` due to starting to use the implementation from
the third-party :pypi:`sphinx-issues` Sphinx extension
-- by :user:`webknjaz`.


- `12531 &lt;https://github.com/pytest-dev/pytest/issues/12531&gt;`_: The coverage reporting configuration has been updated to exclude
pytest&#x27;s own tests marked as expected to fail from the coverage
report. This has an effect of reducing the influence of flaky
tests on the resulting number.

-- by :user:`webknjaz`


- `12533 &lt;https://github.com/pytest-dev/pytest/issues/12533&gt;`_: The ``extlinks`` Sphinx extension is no longer enabled. The ``:bpo:``
role it used to declare has been removed with that. BPO itself has
migrated to GitHub some years ago and it is possible to link the
respective issues by using their GitHub issue numbers and the
``:issue:`` role that the ``sphinx-issues`` extension implements.

-- by :user:`webknjaz`


- `12562 &lt;https://github.com/pytest-dev/pytest/issues/12562&gt;`_: Possible typos in using the ``:user:`` RST role is now being linted
through the pre-commit tool integration -- by :user:`webknjaz`.

8.2.2

=========================

Bug Fixes
---------

- `12355 &lt;https://github.com/pytest-dev/pytest/issues/12355&gt;`_: Fix possible catastrophic performance slowdown on a certain parametrization pattern involving many higher-scoped parameters.


- `12367 &lt;https://github.com/pytest-dev/pytest/issues/12367&gt;`_: Fix a regression in pytest 8.2.0 where unittest class instances (a fresh one is created for each test) were not released promptly on test teardown but only on session teardown.


- `12381 &lt;https://github.com/pytest-dev/pytest/issues/12381&gt;`_: Fix possible &quot;Directory not empty&quot; crashes arising from concurrent cache dir (``.pytest_cache``) creation. Regressed in pytest 8.2.0.



Improved Documentation
----------------------

- `12290 &lt;https://github.com/pytest-dev/pytest/issues/12290&gt;`_: Updated Sphinx theme to use Furo instead of Flask, enabling Dark mode theme.


- `12356 &lt;https://github.com/pytest-dev/pytest/issues/12356&gt;`_: Added a subsection to the documentation for debugging flaky tests to mention
lack of thread safety in pytest as a possible source of flakiness.


- `12363 &lt;https://github.com/pytest-dev/pytest/issues/12363&gt;`_: The documentation webpages now links to a canonical version to reduce outdated documentation in search engine results.

Links

PyPI: https://pypi.org/project/pytest
Changelog: https://data.safetycli.com/changelogs/pytest/

Update pytest-cov from 5.0.0 to 6.0.0.

Changelog

6.0.0

------------------

* Updated various documentation inaccuracies, especially on subprocess handling.
* Changed fail under checks to use the precision set in the coverage configuration.
Now it will perform the check just like ``coverage report`` would.
* Added a ``--cov-precision`` cli option that can override the value set in your coverage configuration.
* Dropped support for now EOL Python 3.8.

Links

PyPI: https://pypi.org/project/pytest-cov
Changelog: https://data.safetycli.com/changelogs/pytest-cov/
Repo: https://github.com/pytest-dev/pytest-cov

Update black from 24.4.2 to 25.1.0.

Changelog

25.1.0

Highlights

This release introduces the new 2025 stable style (4558), stabilizing
the following changes:

- Normalize casing of Unicode escape characters in strings to lowercase (2916)
- Fix inconsistencies in whether certain strings are detected as docstrings (4095)
- Consistently add trailing commas to typed function parameters (4164)
- Remove redundant parentheses in if guards for case blocks (4214)
- Add parentheses to if clauses in case blocks when the line is too long (4269)
- Whitespace before ` fmt: skip` comments is no longer normalized (4146)
- Fix line length computation for certain expressions that involve the power operator (4154)
- Check if there is a newline before the terminating quotes of a docstring (4185)
- Fix type annotation spacing between `*` and more complex type variable tuple (4440)

The following changes were not in any previous release:

- Remove parentheses around sole list items (4312)
- Generic function definitions are now formatted more elegantly: parameters are
split over multiple lines first instead of type parameter definitions (4553)

Stable style

- Fix formatting cells in IPython notebooks with magic methods and starting or trailing
empty lines (4484)
- Fix crash when formatting `with` statements containing tuple generators/unpacking
(4538)

Preview style

- Fix/remove string merging changing f-string quotes on f-strings with internal quotes
(4498)
- Collapse multiple empty lines after an import into one (4489)
- Prevent `string_processing` and `wrap_long_dict_values_in_parens` from removing
parentheses around long dictionary values (4377)
- Move `wrap_long_dict_values_in_parens` from the unstable to preview style (4561)

Packaging

- Store license identifier inside the `License-Expression` metadata field, see
[PEP 639](https://peps.python.org/pep-0639/). (#4479)

Performance

- Speed up the `is_fstring_start` function in Black&#x27;s tokenizer (4541)

Integrations

- If using stdin with `--stdin-filename` set to a force excluded path, stdin won&#x27;t be
formatted. (4539)

24.10.0

Highlights

- Black is now officially tested with Python 3.13 and provides Python 3.13
mypyc-compiled wheels. (4436) (4449)
- Black will issue an error when used with Python 3.12.5, due to an upstream memory
safety issue in Python 3.12.5 that can cause Black&#x27;s AST safety checks to fail. Please
use Python 3.12.6 or Python 3.12.4 instead. (4447)
- Black no longer supports running with Python 3.8 (4452)

Stable style

- Fix crashes involving comments in parenthesised return types or `X | Y` style unions.
(4453)
- Fix skipping Jupyter cells with unknown `%%` magic (4462)

Preview style

- Fix type annotation spacing between * and more complex type variable tuple (i.e. `def
fn(*args: *tuple[*Ts, T]) -&gt; None: pass`) (4440)

Caching

- Fix bug where the cache was shared between runs with and without `--unstable` (4466)

Packaging

- Upgrade version of mypyc used to 1.12 beta (4450) (4449)
- `blackd` now requires a newer version of aiohttp. (4451)

Output

- Added Python target version information on parse error (4378)
- Add information about Black version to internal error messages (4457)

24.8.0

Stable style

- Fix crash when ` fmt: off` is used before a closing parenthesis or bracket. (4363)

Packaging

- Packaging metadata updated: docs are explictly linked, the issue tracker is now also
linked. This improves the PyPI listing for Black. (4345)

Parser

- Fix regression where Black failed to parse a multiline f-string containing another
multiline string (4339)
- Fix regression where Black failed to parse an escaped single quote inside an f-string
(4401)
- Fix bug with Black incorrectly parsing empty lines with a backslash (4343)
- Fix bugs with Black&#x27;s tokenizer not handling `\{` inside f-strings very well (4422)
- Fix incorrect line numbers in the tokenizer for certain tokens within f-strings
(4423)

Performance

- Improve performance when a large directory is listed in `.gitignore` (4415)

_Blackd_

- Fix blackd (and all extras installs) for docker container (4357)

Links

PyPI: https://pypi.org/project/black
Changelog: https://data.safetycli.com/changelogs/black/

Update pre-commit from 3.7.1 to 4.2.0.

Changelog

4.2.0

==================

Features
- For `language: python` first attempt a versioned python executable for
the default language version before consulting a potentially unversioned
`sys.executable`.
 - 3430 PR by asottile.

Fixes
- Handle error during conflict detection when a file is named &quot;HEAD&quot;
 - 3425 PR by tusharsadhwani.

4.1.0

==================

Features
- Add `language: julia`.
 - 3348 PR by fredrikekre.
 - 2689 issue jmuchovej.

Fixes
- Disable automatic toolchain switching for `language: golang`.
 - 3304 PR by AleksaC.
 - 3300 issue by AleksaC.
 - 3149 issue by nijel.
- Fix `language: r` installation when initiated by RStudio.
 - 3389 PR by lorenzwalthert.
 - 3385 issue by lorenzwalthert.

4.0.1

==================

Fixes
- Fix `pre-commit migrate-config` for unquoted deprecated stages names with
purelib `pyyaml`.
 - 3324 PR by asottile.
 - pre-commit-ci/issues234 issue by lorenzwalthert.

4.0.0

==================

Features
- Improve `pre-commit migrate-config` to handle more yaml formats.
 - 3301 PR by asottile.
- Handle `stages` deprecation in `pre-commit migrate-config`.
 - 3302 PR by asottile.
 - 2732 issue by asottile.
- Upgrade `ruby-build`.
 - 3199 PR by ThisGuyCodes.
- Add &quot;sensible regex&quot; warnings to `repo: meta`.
 - 3311 PR by asottile.
- Add warnings for deprecated `stages` (`commit` -&gt; `pre-commit`, `push` -&gt;
`pre-push`, `merge-commit` -&gt; `pre-merge-commit`).
 - 3312 PR by asottile.
 - 3313 PR by asottile.
 - 3315 PR by asottile.
 - 2732 issue by asottile.

Migrating
- `language: python_venv` has been removed -- use `language: python` instead.
 - 3320 PR by asottile.
 - 2734 issue by asottile.

3.8.0

==================

Features
- Implement health checks for `language: r` so environments are recreated if
the system version of R changes.
 - 3206 issue by lorenzwalthert.
 - 3265 PR by lorenzwalthert.

Links

PyPI: https://pypi.org/project/pre-commit
Changelog: https://data.safetycli.com/changelogs/pre-commit/
Repo: https://github.com/pre-commit/pre-commit

Update pylint from 3.2.2 to 3.3.6.

The bot wasn't able to find a changelog for this release. Got an idea?

Links

PyPI: https://pypi.org/project/pylint
Changelog: https://data.safetycli.com/changelogs/pylint/

Update psutil from 5.9.8 to 7.0.0.

Changelog

7.0.0

=====

2025-02-13

**Enhancements**

- 669_, [Windows]: `net_if_addrs()`_ also returns the ``broadcast`` address
instead of ``None``.
- 2480_: Python 2.7 is no longer supported. Latest version supporting Python
2.7 is psutil 6.1.X. Install it with: ``pip2 install psutil==6.1.*``.
- 2490_: removed long deprecated ``Process.memory_info_ex()`` method. It was
deprecated in psutil 4.0.0, released 8 years ago. Substitute is
``Process.memory_full_info()``.

**Bug fixes**

- 2496_, [Linux]: Avoid segfault (a cPython bug) on ``Process.memory_maps()``
for processes that use hundreds of GBs of memory.
- 2502_, [macOS]: `virtual_memory()`_ now relies on ``host_statistics64``
instead of ``host_statistics``. This is the same approach used by ``vm_stat``
CLI tool, and should grant more accurate results.

**Compatibility notes**

- 2480_: Python 2.7 is no longer supported.
- 2490_: removed long deprecated ``Process.memory_info_ex()`` method.

6.1.1

=====

2024-12-19

**Enhancements**

- 2471_: use Vulture CLI tool to detect dead code.

**Bug fixes**

- 2418_, [Linux]: fix race condition in case /proc/PID/stat does not exist, but
/proc/PID does, resulting in FileNotFoundError.
- 2470_, [Linux]: `users()`_ may return &quot;localhost&quot; instead of the actual IP
address of the user logged in.

6.1.0

=====

2024-10-17

**Enhancements**

- 2366_, [Windows]: drastically speedup `process_iter()`_. We now determine
process unique identity by using process &quot;fast&quot; create time method. This
will considerably speedup those apps which use `process_iter()`_ only once,
e.g. to look for a process with a certain name.
- 2446_: use pytest instead of unittest.
- 2448_: add ``make install-sysdeps`` target to install the necessary system
dependencies (python-dev, gcc, etc.) on all supported UNIX flavors.
- 2449_: add ``make install-pydeps-test`` and ``make install-pydeps-dev``
targets. They can be used to install dependencies meant for running tests and
for local development. They can also be installed via ``pip install .[test]``
and ``pip install .[dev]``.
- 2456_: allow to run tests via ``python3 -m psutil.tests`` even if ``pytest``
module is not installed. This is useful for production environments that
don&#x27;t have pytest installed, but still want to be able to test psutil
installation.

**Bug fixes**

- 2427_: psutil (segfault) on import in the free-threaded (no GIL) version of
Python 3.13.  (patch by Sam Gross)
- 2455_, [Linux]: ``IndexError`` may occur when reading /proc/pid/stat and
field 40 (blkio_ticks) is missing.
- 2457_, [AIX]: significantly improve the speed of `Process.open_files()`_ for
some edge cases.
- 2460_, [OpenBSD]: `Process.num_fds()`_ and `Process.open_files()`_ may fail
with `NoSuchProcess`_ for PID 0. Instead, we now return &quot;null&quot; values (0 and
[] respectively).

6.0.0

- 2109_: the namedtuple returned by `disk_partitions()`_&#x27; no longer has
``maxfile`` and ``maxpath`` fields.
- 2396_: `process_iter()`_ no longer pre-emptively checks whether PIDs have
been reused. If you want to check for PID reusage you are supposed to use
`Process.is_running()`_ against the yielded `Process`_ instances. That will
also automatically remove reused PIDs from `process_iter()`_ internal cache.
- 2407_: `Process.connections()`_ was renamed to `Process.net_connections()`_.
The old name is still available, but it&#x27;s deprecated (triggers a
``DeprecationWarning``) and will be removed in the future.

Links

PyPI: https://pypi.org/project/psutil
Changelog: https://data.safetycli.com/changelogs/psutil/
Repo: https://github.com/giampaolo/psutil

pyup-bot added 6 commits March 31, 2025 10:01

Update pytest from 8.2.1 to 8.3.5

8f218ca

Update pytest-cov from 5.0.0 to 6.0.0

e4a34d0

Update black from 24.4.2 to 25.1.0

7e3441e

Update pre-commit from 3.7.1 to 4.2.0

6ae7901

Update pylint from 3.2.2 to 3.3.6

71da3ba

Update psutil from 5.9.8 to 7.0.0

89c8736

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Scheduled weekly dependency update for week 13#228

Scheduled weekly dependency update for week 13#228
pyup-bot wants to merge 6 commits intotrunkfrom
pyup-scheduled-update-2025-03-31

pyup-bot commented Mar 31, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

pyup-bot commented Mar 31, 2025

Update pytest from 8.2.1 to 8.3.5.

8.3.3

8.3.2

8.3.1

8.3.0

8.2.2

Update pytest-cov from 5.0.0 to 6.0.0.

6.0.0

Update black from 24.4.2 to 25.1.0.

25.1.0

24.10.0

24.8.0

Update pre-commit from 3.7.1 to 4.2.0.

4.2.0

4.1.0

4.0.1

4.0.0

3.8.0

Update pylint from 3.2.2 to 3.3.6.

Update psutil from 5.9.8 to 7.0.0.

7.0.0

6.1.1

6.1.0

6.0.0

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant