It supports the client_credentials and authorization code OAuth 2.0 flows. For a complete API Reference checkout [Playlyfe Developers](https://dev.playlyfe.com/docs/api) for more information.
1 maintainer
Metadata
1 maintainer
Release files for playlyfe 0.4.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 |
|---|---|---|---|---|
| playlyfe-0.4.0-2.7.6-none-any.whl | Details for playlyfe-0.4.0-2.7.6-none-any.whl |
Release files / playlyfe-0.4.0-2.7.6-none-any.whl
| Download URL | playlyfe-0.4.0-2.7.6-none-any.whl |
|---|---|
| Size | 3.7 kB |
|
SHA-256 checksum How to use checksums |
be87a2bf2142f582156136a72f84bc1ee0cf9a2056ab11f1204f2cf32d594a7b
|
|
BLAKE2b-256 checksum How to use checksums |
ce5bad74b2ecb46c35c7ea6629444fba1c7a458a5b498d6288fb5e26f6ae4284
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for playlyfe 0.4.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.
