airtight
If you’re going to import antigravity, you’d better make sure the hatch is closed.
The airtight package is written for Python 3.6+. It provides idiosyncratic code that somewhat simplifies the creation and debugging of command-line python scripts.
simpler than a template
Instead of copying some 50-line template for your python script and then writing a bunch of calls to argparse and logging just build some lists describing the arguments and logging level you want and invoke artight.cli.configure_commandline():
#!/usr/bin/env python3
# -*- coding: utf-8 -*-
"""
Example script template using the airtight module
"""
from airtight.cli import configure_commandline
import logging
DEFAULT_LOG_LEVEL = logging.WARNING
OPTIONAL_ARGUMENTS = [
# each argument is a list: short option, long option, default value,
# help string, required?
['-l', '--loglevel', 'NOTSET',
'desired logging level (' +
'case-insensitive string: DEBUG, INFO, WARNING, or ERROR',
False],
['-v', '--verbose', False, 'verbose output (logging level == INFO)',
False],
['-w', '--veryverbose', False,
'very verbose output (logging level == DEBUG)', False],
['-x', '--custom', 7, 'your custom argument', False]
]
POSITIONAL_ARGUMENTS = [
# each argument is a list with 3 elements: name, type, help
['foovar', str, 'some input value that you want']
]
def main(**kwargs):
"""Main function of your script.
kwargs -- keyword arguments as parsed from the command line
"""
# your additional code here
if __name__ == "__main__":
main(**configure_commandline(
OPTIONAL_ARGUMENTS, POSITIONAL_ARGUMENTS, DEFAULT_LOG_LEVEL))
make debug logging just a wee bit easier
The airtight.logging module provides two methods: configure_logging(), which is used by airtight.cli.configure_commandline(), and flog(), which reduces typing when you want to log a variable’s name and value.
So, you can write:
> from airtight.logging import flog
> fish = 'salmon'
> flog(fish)
DEBUG:foo_script: fish: 'salmon'
flog() logs to DEBUG by default, but an optional keyword argument level may be used to specify another standard level, e.g.:
> from airtight.logging import flog
> import logging
> fish = 'salmon'
> flog(fish, level=logging.WARNING)
WARNING:foo_script: fish: 'salmon'
Another optional keyword argument (comment) may be specified. A string value supplied via this argument will be postfixed to the logged variable name and value, thus:
> from airtight.logging import flog
> fish = 'salmon'
> flog(fish, comment='I like this fish!')
DEBUG:foo_script: fish: 'salmon' I like this fish!
etc.
Bug reports and feature requests are welcome, but really I’d prefer pull requests.
todo
docstrings
Metadata
Release files for airtight 0.2.0
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 |
|---|---|---|---|---|
| airtight-0.2.0.tar.gz | 16.9 kB | Without provenance | Details for airtight-0.2.0.tar.gz |
Release files / airtight-0.2.0.tar.gz
| Download URL | airtight-0.2.0.tar.gz |
|---|---|
| Size | 16.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dcfbd8833dd529d6c2ea5601afebf03dc7f624d94fa735cfaa8c6928d120c057
|
|
BLAKE2b-256 checksum How to use checksums |
630a235cdd7fa46383883916e803c71c8f0bb71abd8eed0ba760a9580511de3d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for airtight 0.2.0
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.