Skip to content

Identify Breaking Changes and Compatibility Issues with Python 3.14 #125

@lalitmoza

Description

@lalitmoza

User story

As a : Platform engineer - active user of Polymorphic Chart

I want : systematically analyze the dependencies for compatibility with Python versions 3.14 and later,

so that : We can create a mitigation plan, update our code, and inform users before the new version is released, ensuring a smooth transition and maintaining our project's reliability.

Acceptance criteria

  • Execution of Test Suite against Python 3.14

Given the project's automated test suite (unit, integration, etc.),
When the test suite is executed in the Python 3.14 development environment,
Then the tests must run to completion, and a detailed report must be generated highlighting:

    - [ ] Any tests that fail, indicating a likely breaking change.
    - [ ] Any tests that produce new warnings (e.g., DeprecationWarning), indicating future breaking changes.
    - [ ] The overall test coverage to ensure the suite is effective for this analysis.

Sprint Ready Checklist

    • Acceptance criteria defined
    • Team understands acceptance criteria
    • Team has defined solution / steps to satisfy acceptance criteria
    • Acceptance criteria is verifiable / testable

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingenhancementNew feature or request

    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