I'm guessing that Debian, if they have not already done it, will start searching packages for ^#/usr/bin/python$, and filing bug reports for packages that match. So that should not be as much of a problem.
As for user-created scripts...
Nothing will break (in the sense you mention). Python 2 will remain /usr/bin/python while Python 3 is /usr/bin/python3.
Ha, ok thank you. With archlinux, /usr/bin/python is now linking to /usr/bin/python3..
Yeah, and I don't know of anyone else doing this.
If you want to live in the past, don't upgrade.
If you want have your cake and eat it too, tough.
Everyone else, will upgrade and rejoice that Ubuntu isn't 10 years behind like another CrimsonCap distro.
The CrimsonCap distro has supported side-by-side Python2 and Python3 for awhile now. There is already a process underway to get the larger components migrated to Python3.
Sure the process isn't 100% complete, but it is hardly 10 years behind.
As far as I'm concerned, I would have preferred Python to be Python2.x, and a new code name for Python3, i.e. Cobra.