Use expected pip binary

[mknecht]

try seems to use the system-provided pip binary. (I got the out-of-date warning, which I don't get usually because my user-level pip is up to date.)

This is not what I'd have expected: When I try python packages myself, I of course just type pip install whatever.

[timofurrer]

I think the problem here is that virtualenv is copying the pip and setuptools packages during creation from the system-level and not, as you want, from the user-level.
try itself just calls python -m pip ... which takes the pip from the virtualenv.

The only way I see to fix this is to create the virtualenv with --no-pip and --no-setuptools and somehow install them in the virtualenv manually.
What I don't like about that is the time it would take..

[mknecht]

Hey, you're right and you're right. It's the exact behavior that virtualenv/mkvirtualenv show, and therefore not your problem. Thanks for pointing this out!

Closing.