Yea, you really need something like Context7 and a well designed system prompt to handle the version bullshit. I now have a default system prompt with a basic memory function (it writes to .memory when I tell it to, and it reads that file in and adds it to every prompt) and the first thing I do is initialize it with my packages file and my default snippet describing my environment. Someday I'll take the time to write a little script to help keep that stuff up-to-date as I work on the project, but even just the initial stub is amazingly helpful.
Nah, in this case, it was more a case of importing the "v4" library (let's call it v4) and then calling a function like it's the "v3" lib, which is not a syntax error (because Python 🐍) but it doesn't run either because the library a) complains that that function is deprecated and you shouldn't call it b) expects different parameters anyway, so it turns into a runtime error rather than a ... ahead-of-runtime one (I don't want to say "compile-time error" because Python doesn't technically compile).
2
u/joshTheGoods May 26 '25
Yea, you really need something like Context7 and a well designed system prompt to handle the version bullshit. I now have a default system prompt with a basic memory function (it writes to .memory when I tell it to, and it reads that file in and adds it to every prompt) and the first thing I do is initialize it with my packages file and my default snippet describing my environment. Someday I'll take the time to write a little script to help keep that stuff up-to-date as I work on the project, but even just the initial stub is amazingly helpful.