You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pypandoc brings in an updated pip into the --user site-packages as a dependency, breaking Debian, which relies on its own version of pip. Is a dependency on newer Pip really required by Pandoc? The cascade failure here is very unfortunate.
The result is that all future console invocations of pip on Debian look like...
Traceback (most recent call last):
File "/usr/bin/pip", line 9, in <module>
from pip import main
ImportError: cannot import name main
Debian users are advised not to install pip separately, but to rely on the distro version as discussed here. Of course, if some recursively-retrieved package (like pypandoc) forces the install of a newer version of pip it's pretty much impossible to avoid. I discovered this by installing 'leo'.
The debian approach to wiring pip is deeply stupid it's true, where they should be using python -m pip, they are instead reaching inside the pip package itself for no reason...
~ $ more/usr/bin/pip#!/usr/bin/python# GENERATED BY DEBIANimportsys# Run the main entry point, similarly to how setuptools does it, but because# we didn't install the actual entry point from setup.py, don't use the# pkg_resources API.frompipimportmainif__name__=='__main__':
sys.exit(main())
...but if it's feasible to avoid the updated pip dependency then that would address the issue for a lot of people.
Log showing broken Pip
This log shows how pip breaks through installing Pypandoc (on Ubuntu Artful Aardvark)
It begins with having completely deleted all my --user packages to restore pip function to back out from the previous breakage like...
Hi there,
Pypandoc brings in an updated pip into the --user site-packages as a dependency, breaking Debian, which relies on its own version of pip. Is a dependency on newer Pip really required by Pandoc? The cascade failure here is very unfortunate.
The result is that all future console invocations of pip on Debian look like...
Debian users are advised not to install pip separately, but to rely on the distro version as discussed here. Of course, if some recursively-retrieved package (like pypandoc) forces the install of a newer version of pip it's pretty much impossible to avoid. I discovered this by installing 'leo'.
The debian approach to wiring pip is deeply stupid it's true, where they should be using python -m pip, they are instead reaching inside the pip package itself for no reason...
...but if it's feasible to avoid the updated pip dependency then that would address the issue for a lot of people.
Log showing broken Pip
This log shows how pip breaks through installing Pypandoc (on Ubuntu Artful Aardvark)
It begins with having completely deleted all my --user packages to restore pip function to back out from the previous breakage like...
Initially pip installs go fine, until the line
pip install leo
, which has pypandoc as a dependency, at which point pip is permanently broken.The text was updated successfully, but these errors were encountered: