venv issues

[Nicholas Cole]

On Tue, Nov 3, 2015 at 12:27 PM, Wolfgang Maier
<wolfgang.maier at biologie.uni-freiburg.de> wrote:
> On 03.11.2015 11:32, Nicholas Cole wrote:
>>
>> I'm using python3.5 (installed from binaries) on the latest OS X.
>>
>> I have a curious issue with virtual environments on this machine (but
>> not on my other machine).
>>
>>
>> $ python3.5 -m venv testenv
>> $ source testenv/bin/activate
>> (testenv)$ python -m pip
>> /private/tmp/testenv/bin/python: No module named pip
>> $
>>
>> Logging in as a different user and creating a venv works perfectly, so
>> it's clearly a config issue somewhere, but I've tried removing
>> ~/.bashrc and ~/.bash_profile and that doesn't help.
>>
>> The sys.path for that venv is: ['',
>> '/Library/Frameworks/Python.framework/Versions/3.5/lib/python35.zip',
>> '/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5',
>>
>> '/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/plat-darwin',
>>
>> '/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/lib-dynload',
>> '/private/tmp/testenv/lib/python3.5/site-packages']
>>
>
> Is there something special about your /private/tmp folder? In other words,
> do things work if you create a venv in a different place.
> If you go to /private/tmp/testenv/lib/python3.5/site-packages is there a pip
> folder and what are its permission settings?

/private/tmp/testenv/lib/python3.5/site-packages

is completely empty.

There's nothing special about that folder, though. The problem exists
everywhere.