You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you configure the LM (dspy.settings.configure(lm=lm)) before initializing your modules you get a different prompt to if you configure your LM after initializing your modules.
Since this could be fairly annoying, I'm thinking the following: if we don't release 2.6 (which deletes old clients) within a very short time, we should make them only work if dspy.configure(legacy=True) before any DSPy usage. Once legacy is turned on, it cannot be turned off, i.e. you cannot mix and match 2.5 and 2.4 style DSPy.
That way, we can greatly simplify the if statement causing this issue.
If you configure the LM (
dspy.settings.configure(lm=lm)
) before initializing your modules you get a different prompt to if you configure your LM after initializing your modules.Adds "reasoning" to the output signature.
Adds "rationale" to the output signature.
Think its because the
dspy.settings.lm
is referenced inChainOfThought.__init__
:Maybe something to flag in migration docs or just to be aware of before this logic is removed when
dsp.LM
is removed.The text was updated successfully, but these errors were encountered: