kcaverly
kcaverly
I decided to sneak in a fleshed out JSONBackend, will add tests such that the Predict works with either backend.
This is done, we have feature parity with DSPy from about a week or two ago, prior to COPRO/MIPRO. I think we should merge this with the backend-refactor branch, pull...
I've added an initial global logger, with configuration here: #684. Does the API offered in that PR, cover all the uses outlined here?
Added cache specific settings, with a caching default set to True.
Fixed with #419, for now, you can directly import it with dsp.modules.google import Google.
Thanks @aparnajore, for following up, those have been wrapped up in the PR
Where does the responsibility sit for Parsing the Language Model output to the Signature compliant Structured Output? It is my understanding that the `BaseBackend` would be compatible for the following:...
One thing we may have to tackle, is Template variations on a potentially per backend basis. Ie. For the `JSONBackend`, the guidelines has to be augmented to accommodate for json...
Okay - This guy is good to merge. ### Note on Breaking Changes: This should be entirely backwards compatible with main. I've run a series of the example notebooks to...
@okhat @arnavsinghvi11 are we good to merge this one?