Haha so much. It’s kind of cool, though, because by the time you have figured it all out (and are fighting with the last 10%) some heavies realease a perfect version and you already understand exactly how it works from the ground up and how to use it.
I use function calling to validate the code and that calls a function to save it to a file and from there its in the ide and good to go. Up until recently I was getting full classes of working code.
It was getting so good I let it run shell commands on an airgapped machine I didn’t mind wiping. It did make my hair stand on end before I hit go. Code interpreter style fixing it’s own errors and access to the command line means it could go seriously nuts.
No problems. It would look around for stuff, put things in the right place etc.
python program run other python programs but now i am thinking some sort of unix script
This is an interesting question. exec() is cool and works, but not to my taste. I ended up using subprocess.run() and loving it. So much flexibility. Python calling the shell calling a shell script calling freshly generated python… So badass. It was having that setup in place i was like “Hmmm… should i let gpt4 at it? Yep!!” Just did some tests/experiments definitely not doing that regularly.
(re: subprocess.run() If anyone sees this and doesn’t know what this means read: Very dangerous.)