Booleans, integer division, backwards compatibility; where is Python going?

[phil hunt]

On 5 Apr 2002 16:48:57 GMT, James Logajan <JamesL at Lugoj.com> wrote:
>philh at comuno.freeserve.co.uk (phil hunt) wrote:
>> Another problem is that when a language is constantly changing, it 
>> becomes necessary to constantly relearn it. Python has changed a lot 
>> in the last few years, for example new operators such as +=, and 
>> allowing users to subclass from builtin types, are big (and useful) 
>> changes. Python 1.5.1 was an immature language that could benefit 
>> from changing.
>
>Version 1.5.2 was sufficiently complete and long-lived enough that I 
>established it as the version I would develop against.
>
>> Is there a final destination in sight, which these changes are 
>> leading to?
>
>The answer to this isn't as interesting to me as _when_ will this tinkering 
>end? Something that isn't up for debate: because of the problems I have 
>actually encountered with making code work with the many extant versions of 
>Python, I will no longer be doing any new projects in the language and am 
>not recommending Python to anyone.

This is the situation I wish to avoid.

-- 
<"><"><"> Philip Hunt <philh at comuno.freeserve.co.uk> <"><"><">
"I would guess that he really believes whatever is politically 
advantageous for him to believe." 
                        -- Alison Brooks, referring to Michael
                              Portillo, on soc.history.what-if