pip.exe is missing from the NuGet package

[gipetrou]

BPO	43550
Nosy	@pfmoore, @tjguk, @zware, @eryksun, @zooba

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2021-03-19.05:53:05.840>
labels = ['type-feature', '3.9', 'OS-windows']
title = 'pip.exe is missing from the NuGet package'
updated_at = <Date 2021-03-19.22:18:51.906>
user = 'https://bugs.python.org/gipetrou'

bugs.python.org fields:

activity = <Date 2021-03-19.22:18:51.906>
actor = 'eryksun'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Windows']
creation = <Date 2021-03-19.05:53:05.840>
creator = 'gipetrou'
dependencies = []
files = []
hgrepos = []
issue_num = 43550
keywords = []
message_count = 3.0
messages = ['389055', '389117', '389119']
nosy_count = 6.0
nosy_names = ['paul.moore', 'tim.golden', 'zach.ware', 'eryksun', 'steve.dower', 'gipetrou']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue43550'
versions = ['Python 3.9']

[gipetrou]

When downloading a package from https://www.nuget.org/packages/python the pip.exe is not included. As far as I understand, the recommended way to use pip from a script is to call it from subprocess. Would it be possible to include the exe in the package?

[zooba]

Unfortunately not, because we don't know where it will be installed to, and that executable embeds the full path to its matching python.exe.

I suggest running "python.exe -m pip" instead.

[eryksun]

I suppose if you really need a plain pip command, you could reinstall with python.exe -m pip install --force-reinstall pip.

[aks3090]

whats the timeline of fixing this ?

[zooba]

Whenever pip switches to generating script wrappers with relative paths, or someone contributes an alternate wrapper specifically for the Nuget package.

[pfmoore]

Pip is unlikely to use relative paths, as people use the ability to copy/move the wrapper exe and have it still work. It's relatively easy to write a new wrapper using distlib directly, I believe, but as @zooba says, someone has to contribute the work to make it happen.