Skip to content

Evaluate PyTango upgrade from 10.1.2 to newer version #85

@utkarshp1161

Description

@utkarshp1161

Background

We currently have PyTango 10.1.2 installed. The following newer versions are available on PyPI:

Version Date Type
10.1.3 Feb 10, 2026 Patch
10.1.4 Mar 3, 2026 Patch
10.3.0rc1 May 22, 2026 Release candidate

Before deciding whether to upgrade, we should answer the following questions.


Questions

Functionality

  • Do the newer versions introduce anything useful for our abstraction layer?
  • Are there API changes that would make our code simpler or more ergonomic?
  • Also keeping in mind LLM (agentic) Usage

Breaking Changes

  • Do any versions introduce breaking changes to data structures or interfaces we rely on?
  • Is there a migration guide we need to follow?

Dependencies

  • Do newer versions require a cppTango upgrade? If so, what is the effort?

Testing

  • Do newer versions change behaviour in DeviceTestContext or test utilities that would affect our test suite?
  • Do we need to update mocks or fixtures?

Risk

  • Is 10.3.0rc1 stable enough to track or pin for future adoption?
  • What is the rollback plan if an upgrade breaks something?

References


Suggested Next Steps

  • Read the release notes for 10.1.3, 10.1.4, and 10.3.0rc1
  • Assess impact on our codebase and tests
  • Decide on upgrade target and timeline

Metadata

Metadata

Assignees

No one assigned

    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