Comment by stillsut

16 days ago

I've been finding adding context for your external packages is really important when the package is relatively new and or has breaking changes since the model training cut-off date.

Two that stick out this week are google's genai (client for vertex/gemini ednpoints) that is updating methods and moviepy in their 2.x breaking changes (most of the corpus for this library was trained with v1.x).

I wrote about some findings here, and that there's still not a great way to have the models examine only the pieces of documentation that they need for their work: https://github.com/sutt/agro/blob/master/docs/case-studies/a...

Instruct it to look at the actual code of your dependencies directly. It should be able to (quickly) figure out how the exact version of the dependency you have should be used.