py3k concerns. An example

[Terry Reedy]

"Aaron Watters" <aaron.watters at gmail.com> wrote in message 
news:83ab3b9e-078c-4f5c-82ab-dafd41339dc1 at u36g2000prf.googlegroups.com...

The reason that successive versions of 2.x broke so little is that starting 
at about 2.2, all breakages (starting with int division change) were put 
off until until 3.0 instead of being implemented as decided upon (with 
warning, deprecation, and then removal).  Now the debt comes due.

The new policy of mass breakage was a result of complaint about the old 
policy of gradual breakage.  Of course, the new policy will get complaints 
both from those who preferred the old policy and those who want Python 
frozen with nothing ever removed for improvements.  No change, gradual 
change, and jump change all have problems.

In a year, we will have a better idea of which was better.