[Task]: Improving Beam Python Typehints

[liferoad]

What needs to happen?

Can we make Beam Python Typehints better for Beam 3.0? We should scope the work and then make a good plan to land it for Beam 3.0

Issue Priority

Priority: 2 (default / most normal work should be filed as P2)

Issue Components

• Component: Python SDK
• Component: Java SDK
• Component: Go SDK
• Component: Typescript SDK
• Component: IO connector
• Component: Beam YAML
• Component: Beam examples
• Component: Beam playground
• Component: Beam katas
• Component: Website
• Component: Infrastructure
• Component: Spark Runner
• Component: Flink Runner
• Component: Samza Runner
• Component: Twister2 Runner
• Component: Hazelcast Jet Runner
• Component: Google Cloud Dataflow Runner

[mattalbr]

Just going to put in a pitch for #33802 if we're rethinking type hints for 3.0 -- supporting generics would be really nice

[Abacn]

This Issue is marked as Beam 3 - Milestone 1: No Code and ML focus. Please help us burning down the open blocker tasks.

• If this issue is solved, close it. If it is obsolete, close as not planned. If it is no longer necessary for Beam 3, move it out of the Milestone.

• If the work is pending, please be reminded that Milestone 1 is targeted for completion by Dec 30, 2025

• If this issue involves multiple milestones (e.g. remove a public API should first mark it as deprecated, scoped in Milestone 1; then finally remove it in Beam 3 release candidate, scoped in Milestone 3) and Milestone 1 portion has completed, consider move the Issue to Milestone 3.

[Abacn]

@jrmccluskey I understand typehint has been improved a lot since this is raised. Can we mark this issue as done, or are there still ongoing tasks.

[jrmccluskey]

As far as scoping, I think we're done. We can close this, I can file a tracker for procedural work later

[Abacn]

we can use same tracker and move to milestone 3 (to be closed before first candidate of Beam 3) as well