Skip to content

[Feature Request]: Fully Support Type Checking Callables #34644

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
1 of 17 tasks
jrmccluskey opened this issue Apr 16, 2025 · 0 comments
Open
1 of 17 tasks

[Feature Request]: Fully Support Type Checking Callables #34644

jrmccluskey opened this issue Apr 16, 2025 · 0 comments
Labels
new feature P2 python

Comments

@jrmccluskey
Copy link
Contributor

What would you like to happen?

The Beam Python typing infrastructure used to treat typing.Callable types as Any for checking purposes, and that behavior can break when migrating to the preferred collecitons.abc.Callable types post-PEP-585 implementation. This behavior should be restored in beam type hinting, then later an implementation of a CallableTypeHint class should be created to properly check the inner types of Callables,

Issue Priority

Priority: 2 (default / most feature requests 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
new feature P2 python
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jrmccluskey