aics_pipeline_uploaders
This package contains resources for uploading pipeline data to FMS
aics_pipeline_uploaders==1.2.0
Features
- Store values and retain the prior value in memory
- ... some other functionality
Installation
Stable Release: pip install aics_pipeline_uploaders
Development Head: pip install git+https://github.com/BrianWhitneyAI/aics_pipeline_uploaders.git
Documentation
For full package documentation please visit BrianWhitneyAI.github.io/aics_pipeline_uploaders.
Development
See CONTRIBUTING.md for information related to developing the code.
The Four Commands You Need To Know
-
make installThis will setup a virtual environment local to this project and install all of the project's dependencies into it. The virtual env will be located in
camera-alignment-core/venv. -
make test,make fmt,make lint,make type-check,make import-sortQuality assurance
-
pip install -e .[dev]This will install your package in editable mode with all the required development dependencies.
-
make cleanThis will clean up various Python and build generated files so that you can ensure that you are working in a clean workspace.
Suggested Git Branch Strategy
mainis for the most up-to-date development, very rarely should you directly commit to this branch. GitHub Actions will run on every push and on a CRON to this branch but still recommended to commit to your development branches and make pull requests to main. If you push a tagged commit with bumpversion, this will also release to PyPI.- Your day-to-day work should exist on branches separate from
main. Even if it is just yourself working on the repository, make a PR from your working branch tomainso that you can ensure your commits don't break the development head. GitHub Actions will run on every push to any branch or any pull request from any branch to any other branch. - It is recommended to use "Squash and Merge" commits when committing PR's. It makes
each set of changes to
mainatomic and as a side effect naturally encourages small well defined PR's.
Metadata
Release files for aics-pipeline-uploaders 1.2.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 | |
|---|---|---|---|---|
| aics_pipeline_uploaders-1.2.0.tar.gz | 12.8 kB | Without provenance | Details |
Release files / aics_pipeline_uploaders-1.2.0.tar.gz
| Download URL | aics_pipeline_uploaders-1.2.0.tar.gz |
|---|---|
| Size | 12.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d43cc097551339915e6c1054d96e2dc48c1964ca7bd4094ba2bb6afcc34bec9f
|
|
BLAKE2b-256 checksum How to use checksums |
73321dbe5bc0d8419cb0cb1381dca31655878584abe446275e1ebff8c891a43c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.15
|
Security for aics-pipeline-uploaders 1.2.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.