Background
Currently, the Python components clp-package-utils, clp-py-utils, and job-orchestration use poetry as their build system, while the newer clp-mcp-server uses uv/hatchling. This creates conflicts when trying to establish proper dependencies between components.
Problem
As discussed in PR #1388, the build system incompatibility prevents:
- Direct import of shared constants and utilities between components
- Proper dependency declarations in component manifests
- Running unit tests in isolated environments with component dependencies
Proposed Solution
Migrate clp-package-utils, clp-py-utils, and job-orchestration from poetry to uv to align with the newer clp-mcp-server component and modern Python tooling.
References
Background
Currently, the Python components
clp-package-utils,clp-py-utils, andjob-orchestrationuse poetry as their build system, while the newerclp-mcp-serveruses uv/hatchling. This creates conflicts when trying to establish proper dependencies between components.Problem
As discussed in PR #1388, the build system incompatibility prevents:
Proposed Solution
Migrate
clp-package-utils,clp-py-utils, andjob-orchestrationfrom poetry to uv to align with the newerclp-mcp-servercomponent and modern Python tooling.References