:alt: badge: Supported by Clockwork
:align: right
:target: https://www.clockwork.com/
OpScripts
=========
.. image:: https://img.shields.io/pypi/v/OpScripts.svg
:alt: badge: Python Package Index version
:align: right
:target: https://pypi.python.org/pypi/OpScripts
.. image:: https://img.shields.io/github/tag/ClockworkNet/OpScripts.svg
:alt: badge: GitHub most recent tag
:align: right
:target: https://github.com/ClockworkNet/OpScripts/tags
Python libraries to assist with writing Linux Ops scripts.
Python Compatibility
====================
This library currently requires compatibility with:
.. image:: https://img.shields.io/pypi/pyversions/OpScripts.svg
:alt: badge: Python Package Index supported Python versions
:align: right
:target: https://pypi.python.org/pypi/OpScripts
- 2.6
- 2.7
- 3.4
.. image:: https://img.shields.io/travis/ClockworkNet/OpScripts/master.svg
:alt: badge: Travis CI master branch status
:align: right
:target: https://travis-ci.org/ClockworkNet/OpScripts
However, additional versions are tested automatically.
API Versioning
==============
Each module is versioned so that they can undergo significant changes without
impacting the function and stability of the scripts that use them.
For example::
from opscripts.config import v6 as ops_config
from opscripts.logging import v2 as ops_logging
from opscripts.utils import v8 as ops_utils
For a more in-depth examples, see the:
- `<example.py>`_
- `<example_notify_email.py>`_
- `<example_yaml.py>`_
Dependencies
============
- ``opscripts.config``
- `ConfigArgParse`_
- `PyYAML`_
- ``opscripts.yaml``
- `ordereddict`_ (only required by Python 2.6)
- `PyYAML`_
- Unit Tests
- `mock`_ (only required by Python < 3.3)
- `pytest`_
- `pytest-catchlog`_
- `pytest-colordots`_
- `pytest-flakes`_
- `pytest-localserver`_
- `pytest-pep8`_
- `pytest-pythonpath`_
.. _`ConfigArgParse`: https://github.com/bw2/ConfigArgParse
.. _`PyYAML`: http://pyyaml.org/wiki/PyYAML
.. _`ordereddict`: https://pypi.python.org/pypi/ordereddict/1.1
.. _`mock`: https://pypi.python.org/pypi/mock
.. _`pytest`: http://pytest.org/latest/
.. _`pytest-catchlog`: https://pypi.python.org/pypi/pytest-catchlog
.. _`pytest-colordots`: https://github.com/svenstaro/pytest-colordots
.. _`pytest-flakes`: https://pypi.python.org/pypi/pytest-flakes
.. _`pytest-localserver`: https://pypi.python.org/pypi/pytest-localserver
.. _`pytest-pep8`: http://pypi.python.org/pypi/pytest-pep8
.. _`pytest-pythonpath`: https://pypi.python.org/pypi/pytest-pythonpath
Testing Quick Start
===================
1. Change directory into repository (into same directory as where this README
resides).
2. Install virtual environment::
mkvirtualenv -a . -r tests/requirements.txt opscripts_test
a. If installing requirements errors, update `pip`::
pip install --upgrade pip
b. Install requirements::
pip install -r tests/requirements.txt
3. Run pytest::
py.test
To test against alternate Python versions, it may be useful to create virtual
environments with an interpreter other than the one with which ``virtualenv``
was installed, e.g. for non-default python3::
mkvirtualenv -a . -p $(which python3) -r tests/requirements.txt opscripts_test3
License
=======
.. image:: https://img.shields.io/github/license/ClockworkNet/OpScripts.svg
:alt: badge: GitHub license (MIT)
:align: right
:target: `MIT License`_
- `<LICENSE>`_ (`MIT License`_)
.. _`MIT License`: http://www.opensource.org/licenses/MIT
Metadata
Release files for OpScripts 1.6.7
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 |
|---|---|---|---|---|
| OpScripts-1.6.7.tar.gz | 15.4 kB | Without provenance | Details for OpScripts-1.6.7.tar.gz |
Release files / OpScripts-1.6.7.tar.gz
| Download URL | OpScripts-1.6.7.tar.gz |
|---|---|
| Size | 15.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
04f41d3b169a5eb00bec7f84d34a5c751aa7237a7a4efa689b821d8eae4f335b
|
|
BLAKE2b-256 checksum How to use checksums |
db4c1533d6a9dfba3c9770d74111809560caab504a4e31782434ec021e61a136
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for OpScripts 1.6.7
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.