Utils to support Flask and Sqllite and other connections
1 maintainer
Metadata
1 maintainer
Release files for FlaskerUtil 0.1.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 | |
|---|---|---|---|---|
| FlaskerUtil-0.1.0.tar.gz | 5.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| FlaskerUtil-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.3 kB
Release files / FlaskerUtil-0.1.0.tar.gz
| Download URL | FlaskerUtil-0.1.0.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5ad63f14bde9eaee7c6215180197af475fbde47ba6ef3076f11111ee110e123d
|
|
BLAKE2b-256 checksum How to use checksums |
dd58e4e9fc223fe1f31d3741f4b099f847ec5062b940113b6c7a33222b311360
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.10.11
|
Release files / FlaskerUtil-0.1.0-py3-none-any.whl
| Download URL | FlaskerUtil-0.1.0-py3-none-any.whl |
|---|---|
| Size | 5.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b1f33fcfb4c4ec439750281ab9119d8ffb02e807d7656141ea0be40e3109a937
|
|
BLAKE2b-256 checksum How to use checksums |
dd98249b3d2a704b4045e19249d0f89256d3330cdc7b4cbeffdf911af99369b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.10.11
|
Security for FlaskerUtil 0.1.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.
