Based on Jinja2._compat module. Some py2/py3 compatibility support based on a stripped down version of six so we don’t have to depend on a specific version of it.
1 maintainer
Metadata
1 maintainer
Release files for py3compat 0.4
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 | Reset |
|---|---|---|---|---|
| py3compat-0.4-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Release files / py3compat-0.4-py2.py3-none-any.whl
| Download URL | py3compat-0.4-py2.py3-none-any.whl |
|---|---|
| Size | 5.2 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
8c6a4050cfd2c4e3efe284dee60f67d19f1f774e282fb130d1f58ffa433ccd54
|
|
BLAKE2b-256 checksum How to use checksums |
a2c9b8041f2ec26bc2e57bcc2622a967dc15e42e9728844eb99b9af11bb5e224
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for py3compat 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.
