> And when change finally does happen, it happens in the way most likely to cause everyone heartache, as if to fulfill the prophecy the community made. I assum

> And when change finally does happen, it happens in the way most likely to cause everyone heartache, as if to fulfill the prophecy the community made. I assume you're referring to the 2 to 3 split? Which happened once and every other change has left code in an completely runnable state. Unless you're talking about the C-API then, yeah, it's a PITA to keep it current across versions. Just today I learned about f-strings and previously not knowing about them being added to the language caused me zero heartache -- I could accomplish the exact same things using the other string formatting forms since they still work as designed. Aside from the 2 to 3 thing I'd be interested in a concrete example of a change which caused everyone heartache because, honestly, I've never seen it and I (halfass) follow python development.