SCC
Introduction
The scc command provides tools for simplifying the Git(Hub) workflow.
Documentation
Setup and usage instructions can be found on the OME-contributing pages.
Dependencies
Direct dependencies of scc are:
Installation
To install scc, run:
$ python setup.py install
or using pip, run:
$ pip install scc
To upgrade your pip installation, run:
$ pip install -U scc
Usage
The list of available commands can be listed with:
$ scc -h
For each subcommand, additional help can be queried, e.g.:
$ scc merge -h
Contributing
PyGithub follows PEP 8, the Style Guide for Python Code. Please check your code with pep8 or flake8, the Python style guide checkers, by running flake8 -v . or pep8 -v ..
Running tests
The tests are located under the test directory. To run all the tests, use the test target of setup.py:
python setup.py test
Unit tests
Unit tests are stored under the test/unit folder and can be run by calling:
python setup.py test -t test/unit
Unit tests are also run by the Travis build on every Pull Request opened against the main repository.
Integration tests
Integration tests are stored under test/integration. Many integration tests use snoopys-sandbox and snoopys-sandbox-2 as sandbox repositories to test the scc commands.
Running the integration test suite requires:
a GitHub account
a token-based GitHub connection, i.e. a github.token stored under the local Git configuration file (a global token is ignored):
$ git config github.token xxxx
the user authenticated by the token defined above needs to own forks of snoopys-sandbox and snoopys-sandbox-2
Once this is set up, the integration tests can be run by calling:
python setupy.py test -s test/integration
License
scc is released under the GPL.
Copyright
2012-2019, The Open Microscopy Environment
Release files for scc 0.18.1
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 |
|---|---|---|---|---|
| scc-0.18.1.tar.gz | 47.6 kB | Without provenance | Details for scc-0.18.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| scc-0.18.1-py3-none-any.whl | Python 3 | none | any | Details for scc-0.18.1-py3-none-any.whl |
Total release size: 95.6 kB
Release files / scc-0.18.1.tar.gz
| Download URL | scc-0.18.1.tar.gz |
|---|---|
| Size | 47.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fd6d718a87389168e19913d0fc4ee85be2cee442259c00bb71025b151edf18e8
|
|
BLAKE2b-256 checksum How to use checksums |
b76b23228949101b8700e9ad7d77edadad4a70b4daf1d7175b0b1ab2fd239e18
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.13
|
Release files / scc-0.18.1-py3-none-any.whl
| Download URL | scc-0.18.1-py3-none-any.whl |
|---|---|
| Size | 48.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1f9c1479584298725bda0a8d4d380ba44e5275d4f102d415ec2be3a21080b37b
|
|
BLAKE2b-256 checksum How to use checksums |
84d05707bb655f6006dbb7f96e7c65ae8cb57f9cb0ac8ade389577a445cee8f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.13
|
Security for scc 0.18.1
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.
