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

Tzu-ping Chung added the comment: Yup, seems so. Closing as duplicate then. -- resolution: -> duplicate stage: -> resolved status: open -> closed ___ Python tracker

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

R. David Murray added the comment: This is sounds like a variation on issue 30811. -- nosy: +r.david.murray ___ Python tracker

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

New submission from Tzu-ping Chung : (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