This package aims to provide a simple common framework for console jobs in Python. There is nothing really new about the whole approach and everything can be done using existing tools and packages. SCALYCA just wraps it all together into a reusable class that should be easy to extend for use in batch jobs or simple pipeline stages.
It is supposed to be very lightweight and easily integrable. More complex tasks are probably better suited for custom solutions using the same modules. The programs are not supposed to be interactive, everything has to be initialized either from the command line or, in case of SCALYCA, also from a selectable configuration file.
SCALA -- Simple Console Application with Logging and Argparse
The main class is called Scala. It has two main components:
- Logging, primarily to
stdoutduring the execution of the program. This is implemented with theloggingmodule, using just a single logger. - Parsing and processing command line arguments, that configure the initial state of the application
and tell it what and where should exactly be done. The tool for the job is
argparse.
SCALYCA -- Simple Console Application with Logging, YAML Configuration and Argparse
Scalyca is a subclass of Scala that adds persistent configuration
to the program, which is read from a YAML file during the initialization process,
then stored as a static DotMap from module dotmap.
This is similar to a Python dictionary except that it allows for dot access, which is much more legible.
All of the properties can be overridden from the command line.
The resulting object is accessible through the config variable of the class.
Usage
Just extend the Scala class:
- Static attribute
app_namesets the name of the application that will be displayed byargparse. - Static attribute
descriptionsets the long description forargparse. - In
add_argumentsyou are supposed to add all arguments to the built-inArgumentParser.
1 maintainer
Metadata
1 maintainer
Release files for scalyca 0.2.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 | |
|---|---|---|---|---|
| scalyca-0.2.7.tar.gz | 6.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| scalyca-0.2.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.7 kB
Release files / scalyca-0.2.7.tar.gz
| Download URL | scalyca-0.2.7.tar.gz |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1353b8dd0d575583a86b6094279813d334069738daedbafd2bc97024cb9186ed
|
|
BLAKE2b-256 checksum How to use checksums |
67892a04d2c336b240f5c919d063f956928d84cfe889b68a0a9a68d2c13bd308
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.2.1 CPython/3.12.2 Linux/6.1.0-41-amd64
|
Release files / scalyca-0.2.7-py3-none-any.whl
| Download URL | scalyca-0.2.7-py3-none-any.whl |
|---|---|
| Size | 8.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7b1c7701ddf189615d9d2570195953fe4108a6bc652467e00c6232e39ce75164
|
|
BLAKE2b-256 checksum How to use checksums |
a4fca70425a9c1e3e30793557b394cce1556359ce23de08923aca3ef8bb4c2ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.2.1 CPython/3.12.2 Linux/6.1.0-41-amd64
|
Security for scalyca 0.2.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.
