On Sat, Jul 01, 2017 at 12:45:51AM +0200, Björn Persson wrote:
Adam Williamson wrote:
> Clearly what I meant was "any future non-backwards-compatible major
> Python release". Maybe *right now* you don't expect there to be one,
> but I'm sure there was probably a point during Python 1's lifetime at
> which no-one expected there to be a backwards-incompatible Python 2,
> and a point during Python 2's lifetime at which no-one expected there
> to be a backwards-incompatible Python 3...
Spot on.
There is a Swedish proverb. I don't know whether an English version
exists, but in translation it is: One time is no time; two times is a
habit. Since the Python API has been broken twice, we can expect that
it will be broken again.
"Fool me once, shame on you; fool me twice, shame on me"?
But in this case both parties are one and the same, so "Fool myself
once, shame on me; fool myself twice, shame on me again" which does
not come quite as well ;P
Zbyszek