extension_profiler is a tool to profile compiled code (C/C++/Fortran) from the Python interpreter. It uses the google-perftools CPU profiler and depends on pprof (google-pprof on Debian) for visualization.
Install
This package depends on google-perftools (package google-perftools in Debian). Once you have fulfilled these depencies you can install it with easy_install:
$ easy_install -U yep
or download the package, uncompress and execute the standard command:
$ python setup.py install
However, since the package one-file distribution, you can also just put yep.py somewhere in your $PYTHONPATH.
Usage
There are various ways to use the profiler. The simplest is add this module as argument to the Python interpreter when running your script and add flag -v to visualize the result:
$ python -m yep -v -- my_script.py [arg] ... ...
This will create a file my_script.py.prof that can be analyzed with pprof. Execute python -m yep to get the full list of options.
It is also possible to manually start/stop the profiler from inside Python code:
>>> import yep
>>> yep.start('file_name.prof')
>>> # do your computations
>>> yep.stop()
This will create a file_name.prof to be analized with pperf.
Development
Git repository can be found here:
https://github.com/fabianp/yep
Bugs
Visualize the result with -v will only work on UNIX. An option –prof= would also be nice.
Misc
Author: Fabian Pedregosa <fabian.pedregosa@inria.fr>
License
Simplified BSD License, (C) 2011 Fabian Pedregosa.
Metadata
Release files for yep 0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| yep-0.4.tar.gz | 3.5 kB | Without provenance | Details for yep-0.4.tar.gz |
Release files / yep-0.4.tar.gz
| Download URL | yep-0.4.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
41eac9625335b41657bcaf87083edf9e1a95178ea3c7ad3dd6d6ff5e2fe7ceea
|
|
BLAKE2b-256 checksum How to use checksums |
a67131d335c09755fd8773cb9d66210ff1b1ae34560d9020ac8218c9c51c5e2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for yep 0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.