bzr script hardcoded to /usr/bin/python

[Max Bowsher]

On 15/01/11 00:00, Gordon Tyler wrote:
> As a result of
> https://bugs.launchpad.net/bzr-mac-installers/+bug/702467, I was
> wondering why the bzr script doesn't use "#!/usr/bin/env python" to
> invoke whatever python is on the commandline?

The bzr script in the branch *does* use "#! /usr/bin/env python" - the
shebang is rewritten at install time by distutils - which is actually a
very appropriate thing to do on a typical Linux platform, since you want
to be sure that the bzr script always runs with the same Python
installation which has had bzrlib installed into its library path.

I am not familiar with Mac environments, but in general - and especially
not for things with compiled extensions like bzrlib - using the python
from the PATH is not a good choice, since switching Python installation
would usually require compiling the extensions for the new interpreter.

Max.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/bazaar/attachments/20110117/7378e7c7/attachment.pgp>