This release is a pre-release and may not be stable for production use.
Overview
Development utilities and support code.
Notable packages
-
cli - The codebase's all-in-one CLI. This is not installed as an entrypoint / command when this package is itself installed - that is separated into the
omdev-cliinstallable package so as to not pollute users' bin/ directories when depping this lib for its utility code. -
amalg - The amalgamator.
-
pyproject (amalg) - python project management tool. wrangles but does not replace tools like venv, pip, setuptools, and uv. does things like sets up venvs, generates
.pkgdirectories and theirpyproject.toml's (from their__about__.py's), and packages them. this should grow to eat more and more of the Makefile. as it is amalgamated it requires no installation and can just be dropped into other projects / repos. -
ci (amalg) - ci runner. given a
compose.ymland requirements.txt files, takes care of building and caching of containers and venvs and execution of required ci commands. detects and natively uses github-action's caching system. unifies ci execution between local dev and github runners. -
tools.json (cli:
om j) - a tool for json-like data, obviously in the vein of jq but using the internal jmespath engine. supports true streaming json input and output, as well as various other non-streaming input formats. -
tools.git (cli:
om git) - a tool for various lazy git operations, including the one that (poorly) writes all of these commit messages.
Amalgamation
Amalgamation is the process of stitching together multiple python source files into a single self-contained python script. 'lite' code is written in a style conducive to this.
Local storage
Some of this code, when asked, will store things on the local filesystem. The only directories used (outside of ones explicitly specified as command or function arguments) are managed in home.paths, and are the following:
$OMLISH_HOME, default of~/.omlish- persistent things like config and state.$OMLISH_CACHE, default of~/.cache/omlish- used for things like the local ci cache and various other cached data.
1 maintainer
Metadata
1 maintainer
Release files for omdev 0.0.0.dev410
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 | |
|---|---|---|---|---|
| omdev-0.0.0.dev410.tar.gz | 435.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| omdev-0.0.0.dev410-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 973.3 kB
Release files / omdev-0.0.0.dev410.tar.gz
| Download URL | omdev-0.0.0.dev410.tar.gz |
|---|---|
| Size | 435.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7f38617432efa42d4ee5b45ae5b1d0ff53c439f7cd895fc0b4fda843eb082879
|
|
BLAKE2b-256 checksum How to use checksums |
79243680e68c10b903dd65550efb2734025589553a34f3cb5d3278c838642624
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / omdev-0.0.0.dev410-py3-none-any.whl
| Download URL | omdev-0.0.0.dev410-py3-none-any.whl |
|---|---|
| Size | 537.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e452f1e5d97698fb5873cb7669690ce58bfcfd762cf77a9ce0b2778fc7d27b20
|
|
BLAKE2b-256 checksum How to use checksums |
52c433f309417d5dc664bd18ccbae3d8eae2d6125480490fd5cf40c61542065d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for omdev 0.0.0.dev410
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.
