The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for py-googletrans 4.0.0
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 | |
|---|---|---|---|---|
| py_googletrans-4.0.0.tar.gz | 18.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| py_googletrans-4.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 33.7 kB
Release files / py_googletrans-4.0.0.tar.gz
| Download URL | py_googletrans-4.0.0.tar.gz |
|---|---|
| Size | 18.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0dc45254560cc97076a25e1ef9d67b66024d1f80a0c3f7456c9a99a1726a84a6
|
|
BLAKE2b-256 checksum How to use checksums |
3643b778a254f5a698f90f7087757b03aa911fca2660e04d7ced7d6869f70ebc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.1
|
Release files / py_googletrans-4.0.0-py3-none-any.whl
| Download URL | py_googletrans-4.0.0-py3-none-any.whl |
|---|---|
| Size | 15.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9b735ad33a6042a7fef2d5e3c595dafd4ffe1768e625b7f0a945063a10301037
|
|
BLAKE2b-256 checksum How to use checksums |
18a2e7102ca033307f74d83f5b56cc0dd2e57a63f2c6a1ace3f34bf1c10a40ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.1
|
Security for py-googletrans 4.0.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.
