flaskblocks contains the blocks of code which are commonly used in Flask-powered applications. The goal of this project is to prevent code duplication accross projects by providing a simple way of using different components.
The detailed documentation of this package is available on the source website.
Contributing
The source code is also available. The package is distributed under MIT License.
If you want to have SVN access to the official repository in order to contribute to the project, contact me at arseni.mourzenko@pelicandd.com. If you find it more convinient to clone the source to GitHub, you can do that too.
Metadata
Release files for flask-blocks 1.0.23
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 |
|---|---|---|---|---|
| flask_blocks-1.0.23-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Release files / flask_blocks-1.0.23-py2.py3-none-any.whl
| Download URL | flask_blocks-1.0.23-py2.py3-none-any.whl |
|---|---|
| Size | 11.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
d496eeb9e9bff24130523e2843690f507ef0c7b1a882457f96c0fbec58cfb887
|
|
BLAKE2b-256 checksum How to use checksums |
a00f9d9a30d1b1a50ed9332444064f01b6f3d53a2289c7edcbde102e10a7483d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/42.0.2 requests-toolbelt/0.8.0 tqdm/4.15.0 CPython/3.6.9
|
Security for flask-blocks 1.0.23
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.