MINGW-packages: Wrong dependencies for python-pip

Since when does python-pip depend on so many Python packages?

depends=("${MINGW_PACKAGE_PREFIX}-python-appdirs
         "${MINGW_PACKAGE_PREFIX}-python-cachecontrol"
         "${MINGW_PACKAGE_PREFIX}-python-colorama"
         "${MINGW_PACKAGE_PREFIX}-python-contextlib2"
         "${MINGW_PACKAGE_PREFIX}-python-distlib"
         "${MINGW_PACKAGE_PREFIX}-python-html5lib"
         "${MINGW_PACKAGE_PREFIX}-python-lockfile"
         "${MINGW_PACKAGE_PREFIX}-python-msgpack"
         "${MINGW_PACKAGE_PREFIX}-python-packaging"
         "${MINGW_PACKAGE_PREFIX}-python-pep517"
         "${MINGW_PACKAGE_PREFIX}-python-progress"
         "${MINGW_PACKAGE_PREFIX}-python-pyparsing"
         "${MINGW_PACKAGE_PREFIX}-python-pytoml"
         "${MINGW_PACKAGE_PREFIX}-python-requests"
         "${MINGW_PACKAGE_PREFIX}-python-retrying"
         "${MINGW_PACKAGE_PREFIX}-python-six"
         "${MINGW_PACKAGE_PREFIX}-python-webencodings")

Source: https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-python-pip/PKGBUILD#L15-L31

When I install pip in e.g. a Debian or a Windows, only colorama is installed. Not even wheel is installed, even when nowadays most packages are only delivered in wheel format.

Can you please explain, why a pip in MinGW needs so many dependencies it’s not using at all?

When checking the sources of pip, there is no requirement specified, not even colorama.

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 16 (16 by maintainers)

Most upvoted comments

Fact is pip has no ABI string to distinguish msvc from gcc and that makes it terribly terribly broken for us. Please, if you or anyone who keeps mentioning pip as good-for-msys2 really care so much about pip then please submit patches upstream so we can have an ABI string.

At that point some of my technical objections to pip vanish…

mingwandroid on Jan 7, 2021

In fact I’d rather remove PIP than give the impression that it’s something that’s expected to work well (or at all).

mingwandroid on Jan 6, 2021

Just saying if you look at the tar file of pip from PyPI, you could see a folder called pip/_vendor just looks what’s over there. Similarly, go to C:\msys64\mingw64\lib\python3.8\site-packages\pip and check the _vendor directory. You would be seeing an empty one right?

That’s how it is in package managers, nothing should be vendored, everything should be from the repo. If you got the vendored dependency, you would be missing the patches from this repo, for those packages, and things would be really weird then.

naveen521kk on Jan 4, 2021

@Biswa96 Arch Linux is not a reference (maybe an indication). Only the source code of a package define what is needed and was is unneeded. So if the source code of pip (see link above) doesn’t define dependencies, why is MinGW defining so many dependencies?

If you’re saying MinGW copied dependencies from Arch Linux, then the questions are:

Why has Arch Linux created so many dependencies?
Why does MinGW copy dependencies from Arch Linux?

Paebbels on Jan 4, 2021