Execution Time Wrapper
A simple package with a few method to get the execution time of methods through wrapping.
Usage
Currently, the package contains two methods, one which returns to sdout (print) and one which goes to a logger. The method prints the time in a nice way, i.e. milliseconds, seconds, minutes or hours. For example:
from execution_time_wrapper import get_execution_time_print, get_execution_time_log
@get_execution_time_print
def my_fun():
print("Hello World!")
my_fun()
>> Hello World!
>> Computation time for my_fun: 0.02 ms
However, if the function takes more time:
from execution_time_wrapper import get_execution_time_print, get_execution_time_log
from time import sleep
@get_execution_time_print
def my_fun():
sleep(4)
print("Hello World!")
my_fun()
>> Hello World!
>> Computation time for my_fun: 4.00 s
The same for the other method given, i.e. get_execution_time_log.
TODOs
[ ] Implement logger level
@2022, Leonardo Alchieri
People-Centered Computing Lab - Università della Svizzera italiana, Switzerland
1 maintainer
Metadata
1 maintainer
Release files for execution-time-wrapper 1.0.1
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 |
|---|---|---|---|---|
| execution_time_wrapper-1.0.1.tar.gz | 3.5 kB | Without provenance | Details for execution_time_wrapper-1.0.1.tar.gz |
Release files / execution_time_wrapper-1.0.1.tar.gz
| Download URL | execution_time_wrapper-1.0.1.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a2389b95b7158bb598eede4402cdce3c8b717411023bc1abc1ae1950089634dc
|
|
BLAKE2b-256 checksum How to use checksums |
7516a5d631fdc76f8ea0ef2a152fc327eb95926c8ab0ded92b9adeffcae0a343
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Security for execution-time-wrapper 1.0.1
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.
