Typing stubs for pyaudio
This is an auto-generated PEP 561 type stub package for pyaudio package.
It can be used by type-checking tools like mypy, PyCharm, pytype etc. to check code
that uses pyaudio. The source for this package can be found at
https://github.com/python/typeshed/tree/master/stubs/pyaudio. All fixes for
types and metadata should be contributed there.
See https://github.com/python/typeshed/blob/master/README.md for more details.
This package was generated from typeshed commit 88a8d0ccbceaea769410868d6d1ef1aa25af5ae6.
1 maintainer
Metadata
1 maintainer
Release files for types-pyaudio 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| types_pyaudio-0.2.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for types_pyaudio-0.2.0-py2.py3-none-any.whl |
Release files / types_pyaudio-0.2.0-py2.py3-none-any.whl
| Download URL | types_pyaudio-0.2.0-py2.py3-none-any.whl |
|---|---|
| Size | 3.2 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
ff723b434c1e631655c776be988307cc8e49a7496719313b27003679c1492ea9
|
|
BLAKE2b-256 checksum How to use checksums |
5aa0985dceebbd8df8df2f45bc1c5934696c4eaeab93a859502d7eeb3b0b0d69
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.7.3 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.9.2
|
Security for types-pyaudio 0.2.0
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.
