Skip to content

Migrate Python components from poetry to uv build system #1396

@coderabbitai

Description

@coderabbitai

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:

  1. Direct import of shared constants and utilities between components
  2. Proper dependency declarations in component manifests
  3. 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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions