Align pyEPR dependency management and installation with modern uv-based workflow (as used in Quantum Metal)

[zlatko-minev]

Align pyEPR dependency management and installation with modern uv-based workflow

Description

As part of ongoing efforts to modernize the Quantum Metal ecosystem, we have recently transitioned the Quantum Metal v0.5 development workflow to a uv-based environment setup (fast resolver, reproducible installs, cleaner dependency handling across platforms).

It would be very helpful to explore bringing pyEPR’s dependency management and installation flow into closer alignment with this approach, to improve overall usability and ecosystem consistency.

---

Motivation / Context

• Quantum Metal v0.5 now supports a clean uv workflow for:
  • editable installs from source
  • dev / docs / test extras
  • fast, reproducible environment creation without conda
• pyEPR is frequently used alongside Quantum Metal, and mismatched dependency
  stacks can make combined workflows harder to maintain.
• A shared or compatible install model would reduce friction for users moving
  between the two projects.

---

Proposed Directions (open for discussion)

Some possible (non-exclusive) directions to explore:

• Define or refine a pyproject.toml-based dependency specification compatible with uv
• Provide an optional uv-first installation path (alongside existing approaches)
• Clarify runtime vs development dependencies via extras (e.g. [dev], [docs], [test])
• Where practical, align Python version support and dependency pins with Quantum Metal

This issue is intended as a discussion starter, not a prescriptive plan.

---

Goal

Make it easier for users and contributors to:

• Install pyEPR and Quantum Metal in the same environment
• Use modern, fast tooling (uv) without breaking existing workflows
• Reduce dependency conflicts in multi-tool superconducting-qubit workflows

---

Related

• Quantum Metal v0.5 installation and development workflow
• Ongoing ecosystem alignment across QDC / QDW-supported tooling

[abhishekchak52]

Hi @zlatko-minev, I've started a PR #168 to address this. It's still a work in progress, and the PR draft has more details on the changes. In summary,

• uv should handle all dependencies now. We still need to bump dependency versions to align with Metal.
• Tests are currently broken.
• Readthedocs config manually installs documentation-related dependencies. Testing needed.
• Some unused files/directories were removed.

Looking forward to your feedback on this.

[zlatko-minev]

Very nice, this will be very useful across. On Jan 29, 2026, at 10:57 AM, Abhishek Chakraborty ***@***.***> wrote:abhishekchak52 left a comment (zlatko-minev/pyEPR#167) Hi @zlatko-minev, I've started a PR #168 to address this. It's still a work in progress, and the PR draft has more details on the changes. In summary, uv should handle all dependencies now. We still need to bump dependency versions to align with Metal. Tests are currently broken. Readthedocs config manually installs documentation-related dependencies. Testing needed. Some unused files/directories were removed. Looking forward to your feedback on this. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>