[python] Use wire names in TypedDict docstrings

[Copilot]

TypedDict docstrings in generated types.py were documenting the snake_case client property name even when the emitted TypedDict key uses the camelCase wire name. This updates the generated docstrings to match the actual on-the-wire field names.

• Generator change

  • Update TypedDict docstring generation to use prop.wire_name for types.py Sphinx entries (:ivar: / :vartype:).
  • Preserve existing behavior outside the types-file path, where model/client-facing docstrings still use prop.client_name.

• Regression coverage

  • Add a focused unit test covering a property with:
    • wire name: paramName
    • client name: param_name
  • Assert that generated TypedDict docstrings reference paramName, matching the declared TypedDict field.

• Example

  class Foo(TypedDict, total=False):
      """
      :ivar paramName:
      :vartype paramName: str
      """
  
      paramName: str

• Fixes [python] typeddict camelcase docstrings like on the wire instead of snakecase #11355

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
1 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@typespec/http-client-python@11371

commit: 0adfc0f

[github-actions]

Python emitter diff

Baseline gh:4da8bc856581babb8cb705ed9a0199141dff296b vs this PR.

Diff summary: 61 file(s), +752 / -752

Rendered diff: inline on the run summary, or the emitter-diff-html artifact.

Informational check (eng/emitter-diff); does not block the PR.

[github-actions]

All changed packages have been documented.

• ✅ @typespec/http-client-python

Show changes

@typespec/http-client-python - fix ✏️

Use wire names in TypedDict docstrings

[azure-sdk-automation]

You can try these changes here

🛝 Playground	🌐 Website	🛝 VSCode Extension