Question on AzureOpenAI.py

[qianzheng12]

Hey team, just a quick question, I noticed that in azure_openai.py line 109, we are building self.kwargs with api_base api_version and api_key plus other args. then self.kwargs are used in chat_request in function chat.completions.create. However those three args I mentioned are not expected in chat.completions.create and they are only used to initialise the AzureOpenAiClient. then why are we including them in the self.kwargs ?

(Asking this because it's throwing error for me)

[GautamVhavle]

That file is gone. dspy/azure_openai.py was a thin OpenAI-SDK wrapper that stuffed api_base / api_version / api_key into self.kwargs and then splatted them into chat.completions.create(**self.kwargs). The Azure OpenAI client already consumed those at construction time, so they were extra kwargs on create() and the SDK raised TypeError: Completions.create() got an unexpected keyword argument 'api_base' (or api_version).

Current DSPy does not do that. Configure Azure as a LiteLLM model string:

import dspy

lm = dspy.LM(
    "azure/gpt-4o",
    api_key=os.environ["AZURE_OPENAI_API_KEY"],
    api_base="https://YOUR_RESOURCE.openai.azure.com",
    api_version="2024-08-01-preview",
)
dspy.configure(lm=lm)

api_base / api_version / api_key stay on the LiteLLM client config. They are not forwarded as chat-completion body fields.

If you are still on a 2.4.x tree with AzureOpenAI, either upgrade, or pop those three keys before create():

kwargs = {k: v for k, v in self.kwargs.items() if k not in ("api_base", "api_version", "api_key")}
return self.client.chat.completions.create(**kwargs)

The upgrade is the actual fix. The old class is not maintained.