Skip to content

docs: fix incorrect docstring in AsyncAnthropicFoundry.models#1592

Open
aryanmotgi wants to merge 1 commit into
anthropics:mainfrom
aryanmotgi:fix/foundry-async-docstring
Open

docs: fix incorrect docstring in AsyncAnthropicFoundry.models#1592
aryanmotgi wants to merge 1 commit into
anthropics:mainfrom
aryanmotgi:fix/foundry-async-docstring

Conversation

@aryanmotgi
Copy link
Copy Markdown

Problem

In src/anthropic/lib/foundry.py, the AsyncAnthropicFoundry.models stub docstring still says "Azure Anthropic client", while its synchronous counterpart AnthropicFoundry.models correctly says "Anthropic Foundry client". This looks like a leftover from the rename of the Azure client to the Foundry client.

Evidence

src/anthropic/lib/foundry.py:366 (async):

def models(self) -> None:  # type: ignore[override]
    """Models endpoint is not supported for Azure Anthropic client."""

src/anthropic/lib/foundry.py:183 (sync, the correct phrasing):

def models(self) -> None:  # type: ignore[override]
    """Models endpoint is not supported for Anthropic Foundry client."""

All other "not supported" docstrings in this file consistently say "Anthropic Foundry client" — the async models stub is the only outlier.

Fix

Align the async docstring with the sync one so the user-facing wording is consistent and accurately refers to the Foundry client.

Why it's correct

  • The class itself is AsyncAnthropicFoundry, not an Azure client.
  • Every other stub in the file (batches, sync models, messages, beta) refers to the "Anthropic Foundry client".
  • One-line, docs-only change — no behavioral or type impact.

The async client's models stub said 'Azure Anthropic client' while the
sync AnthropicFoundry.models stub correctly says 'Anthropic Foundry
client'. Align the async docstring with the sync one.
@aryanmotgi aryanmotgi requested a review from a team as a code owner May 23, 2026 00:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant