Arch Linux

Isn't this going to be a problem for files that use #!/usr/bin/python in their header?

This is exactly the thing that it's trying to solve. Files that have #!/usr/bin/python suppose you have python2 installed.

What about when #!/usr/bin/python refers to python3?

And it get's messy when there is multiple programs thinking python points to different versions of python (2/3)

You understood nothing. Come to school with your mom tomorrow.

This is a legitimate concern.
I can't see this "feature request" gaining any credibility without first answering the previous question.
The packages in the repos are packaged assuming python->python3 so there is nothing broken there.
If you introduce a python->python2 optional symlink, the package dependencies will have to be adjusted, a huge headache will ensue, and I can not see this helping out anybody unless those which are too lazy to properly fix their python packages.

"You understood nothing. Come to school with your mom tomorrow."
I beg your pardon? Please elucidate.

Ok so, ideally packages sould have #!/usr/bin/python2 and #!/usr/bin/python3 in their header.
But most packages have #!/usr/bin/python. In this case it should point to python2 (so you would install python2-default), unless you have some special setup and need python3 as default (then install python3-default).

"In this case it should point to python2"
I see this as a packaging problem. Nothing a proper PKGBUILD with some sed/find magic in it can't fix.

Well then, the python2 package should contain the symlink python -> python2, because python2 is supposed to be the default.

python already provides python->python3 which would cause a conflict with python->python2 in the python2 package, making only one version of python possible on a system

it has already been decided that the default python point to python3, http://www.archlinux.org/news/python-is-now-python-3/
and according to the pep you linked to... "python should refer to the same target as python2 but may refer to python3 on some bleeding edge distributions"

So actually no, "because python2 is supposed to be the default" is simply not true.

"Ok so, ideally packages sould have #!/usr/bin/python2 and #!/usr/bin/python3 in their header.
But most packages have #!/usr/bin/python. In this case it should point to python2 (so you would install python2-default), unless you have some special setup and need python3 as default (then install python3-default)."

This in itself shows that the packages are not properly coded and that they should either use python2 or python3 in their headers. Arch shouldn't accommodate incorrect code.

The conclusion appears to be that this bug report is invalid. Candidate for closing.