[egberts1]

As one who programmed Python in Hex-Ray, i was able to find differences in code between two like-binaries in a jiffy (using pseudo-IR tagging that disregards offsets).

Useful in catching modified code (intentional or not).

But that costed us a pretty penny to do just that.

[chucklenorris]

I was just writing some python code these days for ida debugging and a simple dump(type, address) function took me 2 days to implement. I still don't know how to get a tinfo_t from a struc_t. The api is a thin layer over the c++ implementation, is very non pythonic and poorly documented. The debugger freezes so much that i had to use the windbg backend. It still doesn't support multi databases, or at least a builtin way for multiple module analysis in a single session. I have to keep 8 windows open and calculate rvas by hand between them. It doesnt even tell you in which module you end up in, or when it does it's wrong. Not fun. The c decompiler is nice though. But i definitely wouldn't pay my own money for it.

[genmud]

Yep, I had similar stuff about a decade back, probably around the time there was someone who developed python bindings for ida and holy fuck was it painful to do in their official SDK, which IIRC was C++.

Radare2 has some really nice, easily scriptable stuff, you should check it out if you haven't before.