setup when both python2.7 and 3.2 are present is less than clear

[mon_key]

setup when both python2.7 and 3.2 are present is non-trivial.
Not being a pythonista this was anything but clear and it was only after examining the bang line in setup.py that i was able to suss out the problem, namely that:

shell> /usr/bin/env python
=> Python 3.2 (r32:88445, Apr 15 2011, 11:20:08)
[GCC 4.5.2 20110127 (prerelease)] on linux2

Shame on the Bazaar devs for allowing the bzr-fastimport plugin to move a non-distributed dependency to a separate project and not enforcing reasonable documentation constraints for either project!

One almost wonders if such disregard is intentionally promoted to prevent end users from migrating away from bzr. Regardless, I can't get my source history out of bzr and into a git repo fast enough... Phooey and good riddance bzr!

[Jelmer Vernooij (jelmer)]

The 'python' executable has always been used to refer to python 2.x. Some bleeding-edge distributions have moved to 'python' referring to python3 - in this case you should make sure to manually invoke all python2 code with the 'python2' binary.

We're still using 'python' and not 'python2' because the latter isn't available in a lot of older distributions.

See http://www.python.org/dev/peps/pep-0394/ for background.