[New-bugs-announce] [issue32577] Pip creates entry point commands in the wrong place when invoked in a venv nested in a virtualenv

[Tzu-ping Chung]

New submission from Tzu-ping Chung <uranusjr at gmail.com>:

(I’m not sure whether this is a venv or virtualenv problem. Asking here first.)

To reproduce:

    $ python3.6 -m virtualenv outer
    $ ./outer/bin/python -m venv inner
    $ ls inner/bin
    activate  activate.csh  activate.fish  python  python3

In comparison:

    $ python3.6 -m venv another
    $ ls another/bin
    activate         easy_install     pip3             python3
    activate.csh     easy_install-3.6 pip3.6           python3.6
    activate.fish    pip              python

All commands that pip is supposed to populate are missing

Pip can install packages correctly, but the entry points are populated not inside the inner venv, but the outer virtualenv:

    $ ./inner/bin/python -m pip install django
    ....
    $ ls inner/bin
    activate  activate.csh  activate.fish  python  python3
    $ ls outer/bin
    ... django-admin django-admin.py

The entry points correctly point to the inner environment. They are just in the wrong directory.

----------
components: Library (Lib)
messages: 310140
nosy: uranusjr
priority: normal
severity: normal
status: open
title: Pip creates entry point commands in the wrong place when invoked in a venv nested in a virtualenv
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32577>
_______________________________________