To be clear `virtualenv <dir>` will create a Python 2.7 virtualenv, and this works fine.
Use `virtualenv -p python3.4 <dir>` to trigger the described failure, which I've been able to reproduce. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522500 Title: pip in Python 3.4 virtualenvs cannot install using a proxy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1522500/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
