-
-
Notifications
You must be signed in to change notification settings - Fork 511
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Permission denied with Python 3.4 #171
Comments
Original comment by @myint Please see pul request 118 for the fix. |
Original comment by @myint Okay, I see what the problem is. It is caused by the import os
import subprocess
import sys
print('__PYVENV_LAUNCHER__:', os.environ.get('__PYVENV_LAUNCHER__'),
file=sys.stderr)
# The below line fixes the problem shown in tox.
# os.unsetenv('__PYVENV_LAUNCHER__')
process = subprocess.Popen(
['/Users/myint/projects/pep8/.tox/py34/bin/pip',
'install', '--pre',
'-U', '--no-deps',
'/Users/myint/projects/pep8/.tox/dist/pep8-1.5.7a0.zip'])
process.communicate() |
Original comment by @myint Python 3.3 fails, but for a different reason.
And Python 2.7 works fine. This permission problem kind of reminds me of the |
Original comment by @hpk42 Seems like instead of installing into the virtualenv, it goes to the global installation of Python. I don't know but suspect it's an issue with virtualenv/pip/python3.4. Tox is merely triggering the install here. Does it work with python3.3, btw? |
Original comment by @myint Manually installing the virtualenv seems to work fine. Here are a few variations I tried while trying to reproduce it.
I tried installing the zip file that is contained in the tox directory.
And lastly, I tried using the same virtualenv created by tox.
Thanks |
Original comment by @hpk42 what happens if you create a virtualenv yourself and then try to install the same dependencies you specify with tox? |
The text was updated successfully, but these errors were encountered: