Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

python3-pip (18.1) extra-index-url #4011

Closed
cwerther-truce opened this issue Dec 18, 2020 · 4 comments
Closed

python3-pip (18.1) extra-index-url #4011

cwerther-truce opened this issue Dec 18, 2020 · 4 comments

Comments

@cwerther-truce
Copy link

This looks similar to an issue raised for pip (pypa/pip#7486). On my Raspberry Pi 3 running the latest version of Buster and pip3 version 18.1, when I try to install a package from my private index, it fails saying it can't find it on the public index. If I uninstall the version installed via apt and install the latest version of pip (https://pip.pypa.io/en/stable/installing/) using the get-pip.py script, it installs pip version 20.3.3 which successfully installs the package.

@cwerther-truce cwerther-truce changed the title python3-pip extra-index-url python3-pip (18.1) extra-index-url Dec 18, 2020
@XECDesign
Copy link
Contributor

AFAIK, pip moves fairly fast, so the distro-packaged version will always be out of date. One of the first things pip users tend to do is run the pip command to update pip.

@cwerther-truce
Copy link
Author

Fair enough. That being said, 18.1 is a 2018 release and its almost 2021 now. In addition, pip officially recommends not to manually install pip and instead use the one provided by your package manager, so I posted this so that people using the official best practice (from pip at least) to have this work.

@XECDesign
Copy link
Contributor

Yeah, there tends to be a conflict between distros like Debian and fast moving projects like node.js, pip and so on.

This should be something that Debian fixes and if there's a patch that works, I can apply it in Raspberry Pi OS. But I can't pull in a whole new pip release, since I don't know what new issues it will introduce.

@scottamain
Copy link

This is affecting me as well. According to bug #6799 this might have been fixed in pr #6373. And supposedly that was released with pip 19.1 and included with Debian Buster, so I don't understand why RPI OS still has pip 18.1.

Please consider updating this package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants