Cletus is a library to help with commmand line python programs.
It includes: - cletus_config: makes it easy for a program to combine config files, environmental variables, and arguments into a single schema-validated config. - cletus_supp: allows programs and users to “suppress” actions with a program simply by touching a file in a dedicated directory. The suppression action may be to quit, or to simply sleep or temporarily suspend processing. - cletus_log: just boilerplate for common logging. - cletus_job: a well-tested mechanism that uses a pid file to ensure that the same file doesn’t get run twice.
More info is on the cletus wiki here: https://github.com/kenfar/cletus/wiki
Installation
Using pip (preferred) or easyinstall:
~ $ pip install cletus $ easy_install cletus ~
Or install manually from pypi:
~ $ mkdir ~$ wget https://pypi.python.org/packages/source/d/cletus/cletus-0.1.tar.gz $ tar -xvf easy_install cletus $ cd ~-* $ python setup.py install ~
Dependencies
Any of: python 2.7, 3.4, 3.5 or pypy
Licensing
Cletus uses the BSD license - see the separate LICENSE file for further information
Copyright
Copyright 2013, 2014, 2015, 2016 Ken Farmer
v1.0.15 - 2018-05
setup
alter: replace pip’s req module with simple readline to deal with pip 10
v1.0.14 - 2016-08
cletus_logger
add: user-customizable delimiter to log output
v1.0.13 - 2016-05
all
add: minor changes tox.ini to support python 2.7, 3.4, 3.5, and pypy
v1.0.12 - 2015-09
cletus_supp.py
add: silent arg to SuppressCheck() class to suppress all logging. Needed to handle logging volume when continually-checking for suppressions.
v1.0.11 - 2015-05
cletus_config.py
fix: improved defaulting
everything:
ran modernizer to make the code more python3-ready
v1.0.10 - 2015-03
cletus_config.py
fix: diminished logging
v1.0.8 - 2015-01
cletus_config.py
added tests to confirm optional column NULLs
added remove_null_overrides to simplify use
added apply_defaults to simplify use
fix: stopped putting copy of sample configs in /tmp
v1.0.6 - 2014-07
cletus_archiver.py
added comments
added config to setup
v1.0.5 - 2014-07
cletus_archiver.py
moved to script dir from example
setup changed to include archiver & config file
cletus_supp.py
check suppressions directory only when the suppressions method is called, so it can be called repeatedly at checkpoints by an app.
changed suppressions method behavior to default app_name to init app_name.
v1.0.4 - 2014-07
cletus_job
changed to use flock exclusively rather than the pid from the pidfile and a check to see if that pid was still being used. This eliminates a big race condition.
added concurrency testing
cletus_config
added namespace, dictionary and env config inputs
added namespace
added test harness
v1.0.1 - 2014-03
cletus_log
initial add
cletus_config
initial add
cletus_supp
initial add
cletus_job
initial add
1 maintainer
Metadata
1 maintainer
Release files for cletus 1.0.15
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 |
|---|---|---|---|---|
| cletus-1.0.15.tar.gz | 19.5 kB | Without provenance | Details for cletus-1.0.15.tar.gz |
Release files / cletus-1.0.15.tar.gz
| Download URL | cletus-1.0.15.tar.gz |
|---|---|
| Size | 19.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2d92adb4e9044af59a3b491cb16f7cd758787b47ca2e83dcdff8da7cf1e68734
|
|
BLAKE2b-256 checksum How to use checksums |
34ebb956ae3a8a39a7150894a0fbbbede61aaaa7955de72942eef1e9cd0ebd37
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cletus 1.0.15
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.
