Install & Compatibility
Where this runs
tested against v2.2.0 · pip install
no network on importno background threads
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
muslpy 3.10–3.920 runs
installs and imports cleanly · install 0.0s · import 0.000s · 58.2MB
glibcpy 3.10–3.920 runs
installs and imports cleanly · install 6.4s · import 0.000s · 58MB
55MB installed
● package 55MB
Code
Verified usage
Verified import paths — ran on the pinned version, not inferred.
checkmk-dev-tools
✓ This package primarily provides command-line tools, not Python modules for direct import. After installation, scripts are typically accessed via the system PATH.
The 'checkmk-dev-tools' package contains helper scripts meant for direct execution from the command line after being added to the system's PATH. It is not designed for traditional Python `import` statements to access classes or functions programmatically within a Python script. If programmatic interaction is desired, consider executing the CLI tools as subprocesses.
This quickstart demonstrates how to interact with a hypothetical command-line tool from the `checkmk-dev-tools` package using Python's `subprocess` module. Since the package consists of scripts, direct Python imports are not the standard usage. Users are expected to add the installed scripts to their system's PATH and execute them directly.
# Example: Assuming 'cmk-dev-install' is one of the scripts installed and available in PATH
import subprocess
import os
# Note: The actual tools and their arguments depend on the specific scripts
# within the checkmk-dev-tools package and their intended functionality.
# This is a generic example demonstrating how to execute a command-line tool.
# Example of executing a hypothetical 'cmk-dev-info' tool to get version info
# You might need to adjust the command based on actual tools in the package.
try:
result = subprocess.run(['cmk-dev-install', '--help'], capture_output=True, text=True, check=True)
print("cmk-dev-install --help output:\n", result.stdout)
except FileNotFoundError:
print("Error: 'cmk-dev-install' command not found. Ensure checkmk-dev-tools is installed and in PATH.")
except subprocess.CalledProcessError as e:
print(f"Error executing command: {e}")
print(f"Stderr: {e.stderr}")
cmk-dev --version
Debug
Known issues
gotchaThe `checkmk-dev-tools` package installs command-line scripts. These scripts need to be available in your system's PATH environment variable to be executable directly. Installation via pip does not always automatically add scripts to a universally accessible PATH.fixAfter `pip install checkmk-dev-tools`, ensure your shell's PATH includes the directory where pip installs scripts (e.g., `~/.local/bin` or your virtual environment's `bin/Scripts` directory). You might need to restart your terminal or add `export PATH=$PATH:~/.local/bin` to your shell's configuration file (e.g., `.bashrc`, `.zshrc`).
affects: All versions
breakingCheckmk major version upgrades often introduce breaking changes in APIs or internal structures that Checkmk development tools might rely on. Tools might become incompatible or behave unexpectedly with newer Checkmk versions.fixAlways check the official Checkmk release notes and the `checkmk-dev-tools` GitHub repository for specific migration notes and compatibility information before upgrading your Checkmk instance. Update `checkmk-dev-tools` to the latest compatible version.
affects: Across Checkmk major versions (e.g., 2.3.0 to 2.4.0, 2.4.0 to 2.5.0)
gotchaOutput from the scripts can vary significantly based on the Checkmk environment they are executed against (e.g., site version, configuration). Scripts are often designed for specific Checkmk versions or setups.fixConsult the source code or any available documentation for individual scripts within the `checkmk-dev-tools` package to understand their expected behavior, parameters, and environmental dependencies. Test scripts thoroughly in your development environment before relying on them in production-like settings.
affects: All versions
Upgrade
Version history
2.2.0latest on PyPI · released Mar 25, 2026
Audit
Dependencies
No dependency data recorded yet.