Your message dated Sun, 19 Apr 2020 14:22:26 +0200
with message-id <[email protected]>
and subject line Re: Bug#958092: virtualenv: PIP fails with No module named 
'pip._vendor.six'
has caused the Debian Bug report #958092,
regarding virtualenv: PIP fails with No module named 'pip._vendor.six'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
958092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958092
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: virtualenv
Version: 20.0.17-1
Severity: important

Creating a virtualenv no longer works:

$ mkdir /tmp/a
$ cd /tmp/a
$ virtualenv venv
created virtual environment CPython3.8.2.final.0-64 in 443ms
  creator CPython3Posix(dest=/tmp/a/venv, clear=False, global=False)
  seeder FromAppData(download=False, contextlib2=latest, webencodings=latest, 
setuptools=latest, pip=latest, retrying=latest, pep517=latest, requests=latest, 
packaging=latest, certifi=latest, distro=latest, html5lib=latest, 
chardet=latest, distlib=latest, progress=latest, appdirs=latest, 
pkg_resources=latest, msgpack=latest, pytoml=latest, CacheControl=latest, 
wheel=latest, colorama=latest, lockfile=latest, pyparsing=latest, 
urllib3=latest, idna=latest, six=latest, via=copy, 
app_data_dir=/home/arthur/.local/share/virtualenv/seed-app-data/v1.0.1.debian)
  activators 
BashActivator,CShellActivator,FishActivator,PowerShellActivator,PythonActivator,XonshActivator
$ ./venv/bin/pip --version
Traceback (most recent call last):
  File "./venv/bin/pip", line 5, in <module>
    from pip._internal.cli.main import main
  File "/tmp/a/venv/lib/python3.8/site-packages/pip/_internal/cli/main.py", 
line 10, in <module>
    from pip._internal.cli.autocompletion import autocomplete
  File 
"/tmp/a/venv/lib/python3.8/site-packages/pip/_internal/cli/autocompletion.py", 
line 9, in <module>
    from pip._internal.cli.main_parser import create_main_parser
  File 
"/tmp/a/venv/lib/python3.8/site-packages/pip/_internal/cli/main_parser.py", 
line 7, in <module>
    from pip._internal.cli import cmdoptions
  File 
"/tmp/a/venv/lib/python3.8/site-packages/pip/_internal/cli/cmdoptions.py", line 
24, in <module>
    from pip._internal.exceptions import CommandError
  File "/tmp/a/venv/lib/python3.8/site-packages/pip/_internal/exceptions.py", 
line 10, in <module>
    from pip._vendor.six import iteritems
ModuleNotFoundError: No module named 'pip._vendor.six'

I have tried with --download and --no-download, removing ~/.cache/pip
but have not found a way to make a working virtualenv.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.5.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages virtualenv depends on:
ii  python3-virtualenv  20.0.17-1

virtualenv recommends no packages.

virtualenv suggests no packages.

-- no debconf information

-- 
-- arthur - [email protected] - https://people.debian.org/~adejong --

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
--- Begin Message ---
On Sat, 2020-04-18 at 13:50 +0200, Arthur de Jong wrote:
> Creating a virtualenv no longer works:
[...]
> ModuleNotFoundError: No module named 'pip._vendor.six'
> 
> I have tried with --download and --no-download, removing ~/.cache/pip
> but have not found a way to make a working virtualenv.

It turns out the problem is related to NFS (my home directory is NFS
mounted). If I replace ~/.local/share/virtualenv with a symlink to a
local file system everything works as expected.

Sorry for the noise.

-- 
-- arthur - [email protected] - https://people.debian.org/~adejong --

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
_______________________________________________
Python-modules-team mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

Reply via email to