Issue2430

classification
Title: Installed Windows commands are no longer executable
Type: behaviour Severity: urgent
Components: Versions:
Milestone:
process
Status: closed Resolution: duplicate
Dependencies: Superseder:
Assigned To: Nosy List: zyasoft
Priority: urgent Keywords:

Created on 2015-11-14.16:04:29 by zyasoft, last changed 2015-11-15.18:41:18 by zyasoft.

Messages
msg10477 (view) Author: Jim Baker (zyasoft) Date: 2015-11-14.16:04:29
On Windows, bin/pip.exe, etc is no longer installed. Instead, the installation uses non Windows specific installation of commands, including the use of shebang. Example:

c:\jython2.7.1rc\bin>more pip
#!c:\jython2.7.1rc\bin\jython.exe

# -*- coding: utf-8 -*-
import re
import sys

from pip import main

if __name__ == '__main__':
    sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0])
    sys.exit(main())

Most likely introduced by https://hg.python.org/jython/rev/b256a80cbbc5 when I upgraded to upstream wheels for pip/setuptools.

This is a major regression - users can no longer use bin/pip.exe, etc, although bin/jython.exe -m pip is an alternative.

Most likely this will require a small patch to the bundled wheels, most likely setuptools. We will also need to ensure that upstream is changed, so that updating pip/setuptools does not reproduce this regression.

Blocks the release candidate. But should be an easy fix.
msg10481 (view) Author: Jim Baker (zyasoft) Date: 2015-11-15.18:41:17
Duplicate of #2360
History
Date User Action Args
2015-11-15 18:41:18zyasoftsetstatus: open -> closed
resolution: duplicate
messages: + msg10481
2015-11-14 16:04:29zyasoftcreate