| Package | python3-yappi |
| Source | python-yappi |
| Version | 1.4.0-1~bpo11+1 |
| Architecture | amd64 |
| Maintainer | Debian OpenStack |
| Installed-Size | 119 |
| Depends | python3-gevent, python3 (<< 3.10), python3 (>= 3.9~), python3.9:any, python3:any, libc6 (>= 2.17) |
| Filename | pool/bullseye-zed-backports/main/p/python-yappi/python3-yappi_1.4.0-1~bpo11+1_amd64.deb |
| Size | 31356 |
| MD5sum | 4a00198a593d6ad9262a38c5ff900b35 |
| SHA1 | 991ed0e7e9fae1480fc41de5113adffe82421149 |
| SHA256 | d4f1a2d9166030e8078c924a213624ab72981d3eb1856317a50a5e84f95a1d72 |
| Section | python |
| Priority | optional |
| Homepage | https://github.com/sumerc/yappi |
| Description | Yet Another Python Profiler - Python 3.x
Yappi stands for Yet Another Python Profiler. It supports Multithread/CPU time
profiling.
.
CPython standard distribution comes with three profilers. cProfile, Profile
and hotshot. cProfile is implemented as a C module based on lsprof, Profile is
in pure Python and hotshot can be seen as a small subset of a cProfile.
.
The major issue is that all of these profilers lack support for multi-threaded
programs and CPU time.
.
If you want to profile a multi-threaded application, you must give an entry
point to these profilers and then maybe merge the outputs. None of these
profilers are designed to work on long-running multi-threaded application. It
is impossible to profile an application retrieve the statistics then stop and
then start later on the fly (without affecting the profiled application).
.
This package contains the Python 3.x module. |
| Description-md5 | |