Do you QA your Python? Was: 2.1 vs. 2.2

[Dave Kuhlman]

phil hunt <philh at comuno.freeserve.co.uk> wrote:

[snip]

> 
> In summary:
> 
>    New features => good
> 
>    New features that break existing code => bad
> 

Two points:

1. A language that does not progress and change will wither ... and
die ... slowly ...

2. The progression of Python versions has been, for me, very smooth
and orderly.  I have had plenty of time to adapt to and learn to
take advantage of the changes from one version to the next.  I have
been given plenty of information that enabled me to adapt.  Most
changes have been backward compatible.  Very little old code has
broken.

In summary, stop whining.  OK.  I apologize.  And, actually I'm
grateful that there are people like Phil, here, who keep reminding
the Python dev team to think changes and their consequences through
carefully.

But, if you *really* want something to complain about, look at what
happened in the Java community when they had to switch collection
libraries and had to adapt to Swing.  And, I've read that Visual
Basic programmers are going through some very wrenching changes
because of Visual Basic .Net.  Try walking a mile in their shoes. 
Actually, I apologize again.  I wouldn't wish Java or Visual Basic
on anyone. Forcing a Pythonista to program in Java or VB
would be cruel.

  - Dave

-- 
Dave Kuhlman
dkuhlman at rexx.com
http://www.rexx.com/~dkuhlman