http-client-python typeddict enum import

[l0lawrence]

In typeddict mode (alpha)

we make enums literals in types.py, but

we also still try to import the enum from _enums.py as well because it is being used like so in inline def:

[github-actions]

🎯 Issue Triage

In typeddict mode (alpha), the Python client emitter incorrectly generates both enum literals in types.py and an import of the same enum from _enums.py, resulting in a spurious/conflicting import when inline definitions reference that enum.

Category: Bug
Area: emitter:client:python

⚠️ No reproduction code provided (issue uses screenshots only). A minimal TypeSpec snippet that triggers the duplicate enum import in TypedDict mode would help diagnose and fix this.

🔍 Analysis

• Mode affected: TypedDict mode (alpha)
• Root cause: When generating inline definitions, the emitter still adds an import for the enum from _enums.py, even though in TypedDict mode enums are rendered as Literal[...] types in types.py rather than as enum classes. The import-generation path for inline usages does not appear to check whether the enum has been converted to a literal.
• Affected files: types.py (enum literals emitted correctly) and the inline definition codegen that adds the _enums.py import (incorrectly).

📝 Suggested next steps

• Identify the code path in the Python emitter that emits enum imports for inline definitions
• Add a guard: skip generating the _enums.py import when the emitter is in TypedDict mode and the enum is already represented as a literal
• Add a test case covering this scenario

Generated by Agentic Triage