Message 301454 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	Ilya.Kulakov
Recipients	Ilya.Kulakov
Date	2017-09-06.07:59:21
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1504684762.02.0.94557793581.issue31363@psf.upfronthosting.co.za>
In-reply-to

Content
There are 2 venvs. One has the pkg_resources (pkgr_venv) package installed, another (venv) doesn't. Venv without pkg_resources is currently active. Works: $ <pkgr_venv>/python -c "import pkg_resources" Doesn't work: $ python -c "import subprocess; subprocess.check_call(['<pkgr_venv>/python', '-c', 'import pkg_resources'])" Works: $ python -c "import os, subprocess; env = os.environ.copy(); env.pop('__PYVENV_LAUNCHER__'); subprocess.check_call(['< pkgr_venv>/python', '-c', 'import pkg_resources'], env=env)"

There are 2 venvs. One has the pkg_resources (pkgr_venv) package installed, another (venv) doesn't.

Venv without pkg_resources is currently active.

Works: $ <pkgr_venv>/python -c "import pkg_resources"

Doesn't work: $ python -c "import subprocess; subprocess.check_call(['<pkgr_venv>/python', '-c', 'import pkg_resources'])"

Works: $ python -c "import os, subprocess; env = os.environ.copy(); env.pop('__PYVENV_LAUNCHER__'); subprocess.check_call(['< pkgr_venv>/python', '-c', 'import pkg_resources'], env=env)"

History
Date	User	Action	Args
2017-09-06 07:59:22	Ilya.Kulakov	set	recipients: + Ilya.Kulakov
2017-09-06 07:59:22	Ilya.Kulakov	set	messageid: <1504684762.02.0.94557793581.issue31363@psf.upfronthosting.co.za>
2017-09-06 07:59:21	Ilya.Kulakov	link	issue31363 messages
2017-09-06 07:59:21	Ilya.Kulakov	create