Is 3.0 worth breaking backward compatibility?

[walterbyrd]

On Dec 7, 12:35 pm, Andreas Waldenburger <geekm... at usenot.de> wrote:

> Pleeeeze. Python 3 is shipping now, and so is 2.x, where x > 5. Python
> 2 is going to be around for quite some time. What is everybody's
> problem?

A possible, potential, problem, could arise if you were using python
2.x, but some other code, that you wanted to include, was writen in
python 3.x.

It always surprises me that so many python developers never consider
the possibility that you may not always be working with your own code.