dism-core
DIALS Inference Service Manager Core or simply dism-core is a python package that provides core functionality for validating custom YAML templates used to manage custom InferenceService resources in KServe managed by DIALS. It leverages the pydantic library to ensure that the YAML templates conform to the required schema.
[!WARNING] This package is not intended to be installed or used directly. Instead, it serves as a foundational library for other packages that require YAML validation for KServe custom
InferenceServicedeployments.
Development
Install the dependencies and the package using uv:
uv sync --all-groups
uv run pre-commit install
uv pip install -e .
Running tests
Run tests with pytest:
uv run pytest tests
Tox
You may also want to run the tests with tox to test against multiple python versions:
uv run tox
asdf users
tox requires multiple versions of Python to be installed. Using asdf, you have multiple versions installed, but they aren’t normally exposed to the current shell. You can use the following command to expose multiple versions of Python in the current directory:
asdf set python 3.12.9 3.11.10 3.10.13
This will use 3.12.9 by default (if you just run python), but it will also put python3.11 and python3.10 symlinks in your PATH so you can run those too (which is exactly what tox is looking for).
Releasing the package on PyPI
The package is available in PyPI at cmsdials, under the cmsdqm organization. You'll need at leat Mantainer rights to be able to push new versions. This package is not meant to be deployed in PyPI, since it is simply a foundational library for dials-service and dism-cli.
CI
The GitLab CI is configured to automatically publish the release notes in GitLab whever a tag is pushed to the repo.
[!NOTE] For this to work the CI/CD variables named
UV_PUBLISH_TOKENandGITLAB_TOKENshould be registered in gitlab. TheGITLAB_TOKENis a Project Access Token with api read/write rights, which is needed to read merge requests using theglab-cli. https://gitlab.cern.ch/cms-dqmdc/libraries/dism-core/-/settings/access_tokens
Metadata
Release files for dism-core 1.5.1
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 | |
|---|---|---|---|---|
| dism_core-1.5.1.tar.gz | 33.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dism_core-1.5.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 63.3 kB
Release files / dism_core-1.5.1.tar.gz
| Download URL | dism_core-1.5.1.tar.gz |
|---|---|
| Size | 33.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
60ba1e4883c72b8effd922ededb61d0f3c09c056711bd7b91b6ff49cfc68aff8
|
|
BLAKE2b-256 checksum How to use checksums |
037cbeb2e7ac105c4969b0fa2c5633654abc0d5c6cc57b66b9b7a764ae3b293d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.2
|
Release files / dism_core-1.5.1-py3-none-any.whl
| Download URL | dism_core-1.5.1-py3-none-any.whl |
|---|---|
| Size | 30.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
69b3ba100a0d7cb377e36a56927f22e6296daf2fa5edd7d08d48f0e04d955a44
|
|
BLAKE2b-256 checksum How to use checksums |
dc90b6d54c14c23ee7fb5d538ec3c6411ce53cb346c1a57c816f5677555d501b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.2
|
Security for dism-core 1.5.1
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.