Lizard-structure project documentation
Tagline of this app: structure of Lizard, defined and documented in a REST interface.
Most important project links
Code is on github: https://github.com/lizardsystem/lizard-structure
Documentation on readthedocs.org: https://lizard-structure.readthedocs.org/
Tested on travis: https://travis-ci.org/lizardsystem/lizard-structure .
Credits
Reinout van Rees started this library.
Changelog of lizard-structure
0.1 (2012-12-05)
Documented the four core Lizard concepts. [reinout]
Set up documentation generation at https://lizard-structure.readthedocs.org/ . [reinout]
Set up testing on travis: https://travis-ci.org/lizardsystem/lizard-structure . [reinout]
Removed lizard-ui dependency. [reinout]
Initial project structure created with nensskel 1.30.dev0. [reinout]
Release files for lizard-structure 0.1
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 | Actions |
|---|---|---|---|---|
| lizard-structure-0.1.zip | 22.1 kB | Without provenance | Details for lizard-structure-0.1.zip |
Release files / lizard-structure-0.1.zip
| Download URL | lizard-structure-0.1.zip |
|---|---|
| Size | 22.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1f8cc320ecf6c7a3feaf1c20bbd7655e219cb46d102534371286450d72eaa520
|
|
BLAKE2b-256 checksum How to use checksums |
cb39c20f69962ec147bb64f185248bca504c0e59347762cefb99738da6a55830
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for lizard-structure 0.1
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.
