Skip to content
This repository has been archived by the owner on Sep 14, 2018. It is now read-only.

ensurepip does not create pip.exe #1136

Open
ironpythonbot opened this issue Dec 9, 2014 · 4 comments
Open

ensurepip does not create pip.exe #1136

ironpythonbot opened this issue Dec 9, 2014 · 4 comments
Labels
Milestone

Comments

@ironpythonbot
Copy link

It creates pip2.exe and pip2.7.exe in Scripts, but not pip.exe.

Work Item Details

Original CodePlex Issue: Issue 35733
Status: Proposed
Reason Closed: Unassigned
Assigned to: paweljasinski
Reported on: Sat at 11:25 PM
Reported by: jdhardy
Updated on: Sat at 11:25 PM
Updated by: jdhardy

@paweljasinski
Copy link
Contributor

Workaround: provide --default-pip as a parameter to ipy invocation:

ipy -X:Frames -m ensurepip --default-pip --user

I also remember the reason why I got lazy and did not do anything. The pips end up in c:/Users/<auser>/AppData/Roaming/Python/Scripts which is shared across all installed pythons. So there is a potential to overwrite other pip. Using 2 or 2.7 suffix is a coincidence solution. I am not sure what the right solution for shared scripts is. However, having good defaults for ironpython only system should be no effort for user.

@jdhardy
Copy link
Member

jdhardy commented Dec 29, 2014

It really should go into %APPDATA%\IronPython\Scripts or something like
that instead. It doesn't get added to to PATH anyway; the end user still
has to do that.

On Sun, Dec 28, 2014 at 6:48 PM, Pawel Jasinski [email protected]
wrote:

Workaround: provide --default-pip as a parameter to ipy invocation:

ipy -X:Frames -m ensurepip --default-pip --user

I also remember the reason why I got lazy and did not do anything. The pips
end up in c:/Users//AppData/Roaming/Python/Scripts which is shared
across all installed pythons. So there is a potential to overwrite other
pip. Using 2 or 2.7 suffix is a coincidence solution. I am not sure what
the right solution for shared scripts is. However, having good defaults
for ironpython only system should be no effort for user.


Reply to this email directly or view it on GitHub
#1136 (comment).

@native-api
Copy link

Why %APPDATA%? There's "%PROGRAMFILES%\IronPython <version>\Scripts" and that's where it shall go.

@jdhardy
Copy link
Member

jdhardy commented Sep 29, 2015

%PROGRAMFILES% is not writeable by non-Admin users. %APPDATA% is where
regular Python puts it already in a non-elevated context.

On Sun, Sep 27, 2015 at 1:18 PM, native-api [email protected]
wrote:

Why %APPDATA%? There's "%PROGRAMFILES%\IronPython \Scripts" and that's
where it shall go.


Reply to this email directly or view it on GitHub
#1136 (comment)
.

@simplicbe simplicbe added this to the 2.7.7 milestone Aug 4, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

6 participants