Comment 5 for bug 620644
Revision history for this message
| Sridhar Ratnakumar (srid) wrote Re: --user installation leaves bzr.bat broken | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
> I'm looking at your build log here: [snip]
Note that that is using our patched version of bzr (same as the patch in the bug description).
> how is the python shebang at the top of script pointing at the right place
That happens on the user's machine (client). PyPM fixes the shebang line during post-installation ...
> And why is the same path in the bat file any more of a problem?
.. because PyPM only fixes shebang for files that already have it (which is typical for most packages, such as the one using setuptools entry_points even on Windows), and the bzr batch file does not have it.
i.e., pypm automatically fixes shebang in Scripts/bzr - but not Scripts/bzr.bat. Thus, we patched bzr.bat to use the Python interpreter specified in ./bzr.
> I'm interested in fixing the root problem here
The root problem, I suppose, is that bzr's setup.py plainly assumes that the path to Python interpreter remains static from (a) the time "python setup.py build" is run to (b) the point the user can use that package. However, (a) and (b) can happen on a different machine, which is the case with PyPM and possibly with future Windows package managers (I recall one from codeplex or port25)