This release is a pre-release and may not be stable for production use.
a buildout recipe for web application framework aha
1 maintainer
Metadata
1 maintainer
Release files for aha.recipe.gae 0.71bdev
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 | |
|---|---|---|---|---|
| aha.recipe.gae-0.71bdev.tar.gz | 3.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aha.recipe.gae-0.71bdev-py2.5.egg | Legacy Egg format | - | - | Details |
Total release size: 10.5 kB
Release files / aha.recipe.gae-0.71bdev.tar.gz
| Download URL | aha.recipe.gae-0.71bdev.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5b9795753930e9aa28ca681d70ea34491adf875b843757df9915b67e9d976011
|
|
BLAKE2b-256 checksum How to use checksums |
ad6023df5df4337ed2964550fc24ec7b31c439d495ba9b96955de45d76b51d1a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / aha.recipe.gae-0.71bdev-py2.5.egg
| Download URL | aha.recipe.gae-0.71bdev-py2.5.egg |
|---|---|
| Size | 7.2 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
eb658c441f2a1f1038d566c1eda9d21eb0e40b4e87d059a90335ee2602ef59fb
|
|
BLAKE2b-256 checksum How to use checksums |
948e92cea1fa3b7d1c80e2efe71a1f3a5e1fd2d8c2befd015ffe47e6c900cecc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for aha.recipe.gae 0.71bdev
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.
