On Sun, 20 Nov 2016 19:17:49 +0000, Tobias Hansen <than...@debian.org> wrote:
> If you google this you see that tons of people have similar issues: > https://github.com/ipython/ipython/issues/9656 > https://github.com/ipython/ipython/issues/9815 > https://github.com/chrippa/backports.shutil_get_terminal_size/issues/9 > The most common "solution" there is reinstalling something with > pip. My suspicion is that the people who see this on Debian also used > pip and there is something interfering. Did you guys use pip (or > something else to install Python modules not from Debian) and have a > backports module or backports.shutil_get_terminal_size itself > installed there? I do use pip within virtual environments, but these shouldn't interfere. First, as per Julien's request, here's my output: $ python Python 2.7.12+ (default, Sep 1 2016, 20:27:38) [GCC 6.2.0 20160927] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from backports.shutil_get_terminal_size import get_terminal_size Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: No module named shutil_get_terminal_size When using pip within virtual environments, packages/modules get installed in ~/.local/lib/python2.7 in my case. There I see one potentially interfering backports module, which shows these contents: $ ls -alh ~/.local/lib/python2.7/site-packages/backports/ total 12K drwxr-xr-x 3 sluque sluque 4.0K Oct 30 16:16 . drwx------ 20 sluque sluque 4.0K Oct 30 16:18 .. drwxr-xr-x 2 sluque sluque 4.0K Oct 30 16:16 configparser -- Seb
