This library is a fork of George Notaras’ python-ping library, which is an implementation of the standard ICMP ping in pure Python.
As it uses raw ICMP sockets, you need to be root to use the functions exported by the ping module.
This fork by Pierre Bourdon adds a setup.py file in order to permit an easier distribution of the package. The license of the library remains unchanged (GPLv2), see COPYING.
Metadata
Release files for ping 0.2
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 |
|---|---|---|---|---|
| ping-0.2.tar.gz | 11.0 kB | Without provenance | Details for ping-0.2.tar.gz |
Release files / ping-0.2.tar.gz
| Download URL | ping-0.2.tar.gz |
|---|---|
| Size | 11.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ecb32294c2af8ae075de4a3743f568db376480ad81c2e010a7f1ce1cee7b030f
|
|
BLAKE2b-256 checksum How to use checksums |
03ac9a3f332f8d7d27cd8929922b2e225842c1623760364b37fc79dc0f65e77d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ping 0.2
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.