Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#61930 - [python-pip][python-progress] pip broken with python-progress 1.5

Attached to Project: Community Packages
Opened by Felix Cobos (fcobos) - Thursday, 07 March 2019, 05:45 GMT
Last edited by Eli Schwartz (eschwartz) - Tuesday, 12 March 2019, 18:11 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Felix Yan (felixonmars)
Eli Schwartz (eschwartz)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 18
Private No

Details

Description:
python-progress 1.5 seems to break pip.
Downgrading to python-progress 1.4 fixes it.

Additional info:
* package version(s) 18.1-1


Steps to reproduce:
pip -h
Traceback (most recent call last):
File "/usr/bin/pip", line 11, in <module>
load_entry_point('pip==18.1', 'console_scripts', 'pip')()
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 489, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 2793, in load_entry_point
return ep.load()
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 2411, in load
return self.resolve()
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 2417, in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/usr/lib/python3.7/site-packages/pip/_internal/__init__.py", line 40, in <module>
from pip._internal.cli.autocompletion import autocomplete
File "/usr/lib/python3.7/site-packages/pip/_internal/cli/autocompletion.py", line 8, in <module>
from pip._internal.cli.main_parser import create_main_parser
File "/usr/lib/python3.7/site-packages/pip/_internal/cli/main_parser.py", line 8, in <module>
from pip._internal.cli import cmdoptions
File "/usr/lib/python3.7/site-packages/pip/_internal/cli/cmdoptions.py", line 22, in <module>
from pip._internal.utils.ui import BAR_TYPES
File "/usr/lib/python3.7/site-packages/pip/_internal/utils/ui.py", line 15, in <module>
from pip._vendor.progress.helpers import HIDE_CURSOR, SHOW_CURSOR, WritelnMixin
ModuleNotFoundError: No module named 'pip._vendor.progress.helpers'
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Tuesday, 12 March 2019, 18:11 GMT
Reason for closing:  Fixed
Additional comments about closing:  python-pip 18.1-2
Comment by Eli Schwartz (eschwartz) - Thursday, 07 March 2019, 06:33 GMT
  • Field changed: Summary ([python-progress] pip broken with python-progress 1.5 → [python-pip][python-progress] pip broken with python-progress 1.5)
  • Field changed: Status (Unconfirmed → Assigned)
  • Task assigned to Felix Yan (felixonmars), Eli Schwartz (eschwartz)
Comment by N.E. Neal (neneal) - Sunday, 10 March 2019, 18:18 GMT
Note that python-pip is also substantially out of date.
Comment by Sylvain Prigent (slybzh) - Tuesday, 12 March 2019, 10:57 GMT
A workaround that worked for me (might be useful for others)
- uninstall pip
- remove the folder "/usr/lib/python3.7/site-packages/pip/"
- reinstall pip

One big difference between a fresh install after deleting manually the folder and keeping it, is that the "_vendor" subfolder does not contain "progress" any more (and pip is now working perfectly).
Comment by Eli Schwartz (eschwartz) - Tuesday, 12 March 2019, 18:11 GMT
_vendor should not contain anything unless you broke your installation by using sudo pip install pip, in which case no guarantees can be made of anything at all, ever. If so, pleas pacman -S lostfiles and run the lostfiles script to find files in your /usr that do *not* belong there.

At any rate, pip is now updated to work with progress 1.5, so this is no longer an issue.

Loading...