Catalog PyPI
PACKAGE EXPLORERView in registry

aics-pipeline-uploaders

PyPI

This package contains resources for uploading pipeline data to FMS

Versions collected1
Direct dependencies0From release 1.2.0
Last observed21 Oct, 10:21 UTC

README

Version 1.2.0 documentation

aics_pipeline_uploaders

Build Status Documentation Code Coverage

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

  1. make install

    This 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.

  2. make test, make fmt, make lint, make type-check, make import-sort

    Quality assurance

  3. pip install -e .[dev]

    This will install your package in editable mode with all the required development dependencies.

  4. make clean

    This 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

  1. main is 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.
  2. 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 to main so 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.
  3. It is recommended to use "Squash and Merge" commits when committing PR's. It makes each set of changes to main atomic and as a side effect naturally encourages small well defined PR's.

Downloads & popularity

Awaiting observations

No metric observations yet

Download counts and popularity will appear here as the collector receives them.

Versions 1

Collected releases
VersionPublishedDirect dependenciesOpen version
1.2.029 Jun 20230

Package advisories

0
No matching advisories collected

This describes our collected data; it is not a security assessment.

Repository

PENDING
aics-int/aics_pipeline_uploaders

Shared repository data · GitHub

License detected in repository
Not collected

Metadata history

Meaningful changes
Current collected state Current

Observed since 21 Oct, 10:21 UTC

No superseded metadata states collected. Unchanged observations do not create new revisions.

Record identity

package:60080434501a020ca19ef906c2afd47b8fec8a4b86e6e0877ca7f84aa1f08963