Issue 32577: Pip creates entry point commands in the wrong place when invoked in a venv nested in a virtualenv (original) (raw)

Issue32577

Created on 2018-01-17 06:14 by uranusjr, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (3)
msg310140 - (view)	Author: Tzu-ping Chung (uranusjr) *	Date: 2018-01-17 06:14
(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.
msg310159 - (view)	Author: R. David Murray (r.david.murray) *	Date: 2018-01-17 13:16
This is sounds like a variation on issue 30811.
msg310183 - (view)	Author: Tzu-ping Chung (uranusjr) *	Date: 2018-01-17 15:05
Yup, seems so. Closing as duplicate then.