TP> Don't think Linux is immune either. Upgrading gcc or glibc TP> can "suddenly break" programs that used to work fine. God has TP> a sense of humor about this, though: He usually arranges that TP> breakage show up first in obscure libm endcases <wink>.
Or upgrade a supposedly backwards compatible library, like, oh I dunno, libz?
>> ... We're really touching on much deeper flaws in software >> development, with no good answers, IMO. TP> Indeed so! Python's not the only thing that changes in TP> incompatible ways over time: *everything* does, including the TP> compilers, system libraries, system tools, and OS policies.
Heck, I wash my pillow and I can't sleep right for weeks.
TP> For this reason, I suggest naming the hypothetical "forward TP> and backward compatible forever more" Python branch the TP> "Python Acrostics and Beekeeping" branch. TP> you-can't-spell-pablum-without-pab-ly y'rs - tim
Or how about the "Garth Releases" (named after character in Wayne's World who utters the immortal truth "We fear change").