That is fine unless the Python development team has decide that python3 will not become python.
Python 2.7.x will be maintained for quite some time. (In excess of four more years.) Even after it is dropped in the future there's no indication that the python3 binary is intended to become the python binary. The link I posted earlier to the thread on the Python mailing list seems to indicate the opposite. On Oct 20, 2010, at 10:32, C Anthony Risinger <anth...@extof.me> wrote: > I think what Arch is doing is perfectly reasonable; if you, as a > developer, or even a user, run the `python` binary, you should not > expect any assurances, as you are making assumptions about the target > environment. If your app requires a particular major or minor version > to operate correctly, then make this clear in the shebang, throw an > exception, etc... imo, catering to sluggish apps that are not py3k > compatible and not active enough to even acknowledge the onset of > py3k, is a waste of time.
