On Tue, Nov 3, 2015 at 1:59 PM, Chris Angelico wrote:
> On Tue, Nov 3, 2015 at 9:32 PM, Nicholas Cole wrote:
>> 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'
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/
On Tue, Nov 3, 2015 at 9:32 PM, Nicholas Cole wrote:
> 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.
What happens if you create a brand new user, then c
On Tue, Nov 3, 2015 at 12:27 PM, Wolfgang Maier
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 -
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
/privat