Bazaar on Windows uses a bat file to launch not an exe
Bug #1431336 reported by
Paul Moore
This bug report is a duplicate of:
Bug #329207: Optionally support installing bzr.py script rather than bzr.bat on Windows.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
The Windows installers for Bazaar install a "bzr.bat" file to run Bazaar. Unfortunately, bat files are not treated as "first class citizens" by Windows and this causes a number of issues:
1. Running Bazaar via subprocess.Popen fails (this has resulted in a bug in pip's Bazaar support, see https:/
2. It is not possible to execute Bazaar from another bat file without using the CALL statement ("CALL bzr ...", rather than just "bzr ...").
Setuptools entry points generate real exe files which suffer from none of the above issues.
Please consider switching to using setuptools entry points or some other means of providing the bzr command via a genuine "exe" file on Windows.
Revision history for this message
| Paul Moore (pmoore) wrote | #1 |
| tags: | added: win32 |
| Changed in bzr: | |
| status: | New → Confirmed |
| tags: | added: check-for-breezy |
To post a comment you must log in.
Further comment - the Windows installers for Bazaar *do* provide a bzr.exe command. This issue only applies when you use setup.py to install Bazaar into your existing Python installation. Sorry for the confusion.