Skip to main content

Generated from aind-library-template

Project description

aind-data-transfer-models

License Code Style semantic-release: angular Interrogate Coverage Python

Usage

For more detailed examples, please check out the readthedocs.

Installation

  • From pypi, run
pip install aind-data-transfer-models
  • From git, in the root directory, run
pip install -e .

To develop the code, run

pip install -e .[dev]

Contributing

Linters and testing

There are several libraries used to run linters, check documentation, and run tests.

  • Please test your changes using the coverage library, which will run the tests and log a coverage report:
coverage run -m unittest discover && coverage report
  • Use interrogate to check that modules, methods, etc. have been documented thoroughly:
interrogate .
  • Use flake8 to check that code is up to standards (no unused imports, etc.):
flake8 .
  • Use black to automatically format the code into PEP standards:
black .
  • Use isort to automatically sort import statements:
isort .

Pull requests

For internal members, please create a branch. For external members, please fork the repository and open a pull request from the fork. We'll primarily use Angular style for commit messages. Roughly, they should follow the pattern:

<type>(<scope>): <short summary>

where scope (optional) describes the packages affected by the code changes and type (mandatory) is one of:

  • build: Changes that affect build tools or external dependencies (example scopes: pyproject.toml, setup.py)
  • ci: Changes to our CI configuration files and scripts (examples: .github/workflows/ci.yml)
  • docs: Documentation only changes
  • feat: A new feature
  • fix: A bugfix
  • perf: A code change that improves performance
  • refactor: A code change that neither fixes a bug nor adds a feature
  • test: Adding missing tests or correcting existing tests

Semantic Release

The table below, from semantic release, shows which commit message gets you which release type when semantic-release runs (using the default configuration):

Commit message Release type
fix(pencil): stop graphite breaking when too much pressure applied Patch Fix Release, Default release
feat(pencil): add 'graphiteWidth' option Minor Feature Release
perf(pencil): remove graphiteWidth option

BREAKING CHANGE: The graphiteWidth option has been removed.
The default graphite width of 10mm is always used for performance reasons.
Major Breaking Release
(Note that the BREAKING CHANGE: token must be in the footer of the commit)

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

aind_data_transfer_models-0.14.0.tar.gz (48.3 kB view details)

Uploaded Source

Built Distribution

aind_data_transfer_models-0.14.0-py3-none-any.whl (13.9 kB view details)

Uploaded Python 3

File details

Details for the file aind_data_transfer_models-0.14.0.tar.gz.

File metadata

File hashes

Hashes for aind_data_transfer_models-0.14.0.tar.gz
Algorithm Hash digest
SHA256 5790fa338f0565de35d75b4448423515cdf02402c740d48ed55ed56e4d70343d
MD5 c8eebe7bcbda062fd867377c480a53b0
BLAKE2b-256 ae33771dd9ef3bf709d77c250fdcf62e3a15c766eded725c56caafe510a6596a

See more details on using hashes here.

Provenance

File details

Details for the file aind_data_transfer_models-0.14.0-py3-none-any.whl.

File metadata

File hashes

Hashes for aind_data_transfer_models-0.14.0-py3-none-any.whl
Algorithm Hash digest
SHA256 c594297a7b01f57681962ca4d0b93d6b37e29fa62866a2f4170303320f689987
MD5 5a5029940a58c5f2c5a43185b65aede6
BLAKE2b-256 b1e498cfd9aa1910121297551b1981949f5d59f75680d1530291b609e6d33986

See more details on using hashes here.

Provenance

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page