eke.labcas
This package provides the display of LabCAS information in the EDRN portal.
Notes
Installation
Use Buildout with the plone.recipe.zope2instance recipe. Add eke.labcas to the list of eggs to install; or, include eke.labcas as a dependency of another egg.
You don’t need to specify a “ZCML slug” since this package uses z3c.autoinclude.
Changelog
What follows is a history of changes from release to release. Where issue IDs are listed below, you can find out more about them by visiting the issue tracker at https://oodt.jpl.nasa.gov/jira/browse/CA.
0.0.3 — Plone 4.3.9 Upgrade
CA-1592
0.0.2 — An Image Is Worth 1K Words
CA-1296 - Imaging libray missing
0.0.1 — I Had Some Chicken; Pass Me the FLOSS
First official release as free/libre/open source software.
0.0.0 — Unreleased
This release is not released. Neat, huh?
Release files for eke.labcas 0.0.3
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 |
|---|---|---|---|---|
| eke.labcas-0.0.3.zip | 34.4 kB | Without provenance | Details for eke.labcas-0.0.3.zip |
Release files / eke.labcas-0.0.3.zip
| Download URL | eke.labcas-0.0.3.zip |
|---|---|
| Size | 34.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
703b984e4d98374a2b3d27fb00be55c08c5b666d0fee98a657037650027bd832
|
|
BLAKE2b-256 checksum How to use checksums |
0e721052137ab12a9d91f98427677987ca3bf14f8c454a28e0bd73057f7e5c3c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/2.7
|
Security for eke.labcas 0.0.3
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.
