python-psutil
A graphical interface that lets you easily analyze and introspect unaltered running Python processes.
- Developed at devel:languages:python
- Sources inherited from project openSUSE:Factory
-
8
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory:Rebuild/python-psutil && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
mem-used-bsc1181475.patch | 0000001251 1.22 KB | |
psutil-5.9.5.tar.gz | 0000493489 482 KB | |
python-psutil.changes | 0000069076 67.5 KB | |
python-psutil.spec | 0000003297 3.22 KB | |
skip_failing_tests.patch | 0000007147 6.98 KB | |
skip_rlimit_tests_on_python2.patch | 0000002398 2.34 KB |
Revision 73 (latest revision is 82)
Dominique Leuenberger (dimstar_suse)
accepted
request 1084220
from
Dirk Mueller (dirkmueller)
(revision 73)
- update to 5.9.5: * in case of exception, display a cleaner error traceback by hiding the `KeyError` bit deriving from a missed cache hit. * print the full traceback when a `DeprecationWarning` or `UserWarning` is raised. * there are cases where `Process.cwd()`_ cannot be determined (e.g. directory no longer exists), in which case we returned either ``None`` or an empty string. This was consolidated and we now return ``""`` on all platforms. * [UNIX]: if process is a zombie, and we can only determine part of the its truncated `Process.name()`_ (15 chars), don't fail with `ZombieProcess`_ when we try to guess the full name from the `Process.cmdline()`_. Just return the truncated name. * on certain kernels, ``"MemAvailable"`` field from ``/proc/meminfo`` returns ``0`` (possibly a kernel bug), in which case we calculate an approximation for ``available`` memory which matches "free" CLI utility. * `disk_partitions()`_: do not unnecessarily read /proc/filesystems and raise `AccessDenied`_ unless user specified `all=False` argument. * `users()`_ loses precision for ``started`` attribute (off by 1 minute). * if cwd no longer exists. Return an empty string instead.
Comments 0