Package: python3-pip Version: 1.4.1-2 Followup-For: Bug #692108 Dear Maintainer, *** Please consider answering these questions, where appropriate ***
* What led up to the situation? In a directory with $ virtualenv venv --distribute then $ . venv/bin/actvate Installing with pip3 as a non-priveleged user, pip3 tries to install in /usr/bin at least for $ pip3 install Django This is not the case and the install completes for a non-priveleged user when invoked by $ pip install Django * What exactly did you do (or not do) that was effective (or ineffective)? $pip3 install --user Django Gets around this problem (but I didn't know this, until I read this bug.) * What was the outcome of this action? The $ pip3 install Django fails to install for a non-privleged user. * What outcome did you expect instead? To install in the virtualenv the package Django *** End of the template - remove these lines *** -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python3-pip depends on: ii ca-certificates 20130906 ii python3 3.3.2-17 ii python3-pkg-resources 2.1-1 ii python3-setuptools 2.1-1 Versions of packages python3-pip recommends: ii build-essential 11.6 ii python3-dev 3.3.2-17 python3-pip suggests no packages. -- no debconf information _______________________________________________ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team