Comment 2 for bug 1250088

Over in debian-python, issues like this come up from time to time in other packages which provide version-specific cli's. There's still debate over best practices here, but I think we're coming close to the following convention:

* The script should always be invocable by -m, e.g. `$python -m jsonpatch` so that if $python is `python3` or `python2.7` or whatever, it will always do the right thing.

* Install a /usr/bin/jsonpatch3 which has a #! line of /usr/bin/python3

* Install a /usr/bin/jsonpatch which has a #! line of /usr/bin/python

* Optionally, if the script is dependent on the Python minor version, then install /usr/bin/jsonpatch-2.7 (with or without dash, but the dash seems more common), with a #! line of /usr/bin/python2.7

* Similarly for Python 3.X

You've prompted me to try to revive this discussion on debian-python, so we can at least come to some (documented!) conventions. But I think the above is the general shape of what we seem to do these days.