Indeed! I've typed “pip install -U pip” so many times I thought they were all up to date. thanks, -steve

On Jun 27, 2016, at 7:57 PM, Robert Collins wrote:

Its almost certainly the version of pip within each environment.

-Rob

On 27 June 2016 at 23:45, Steve Spicklemire wrote:

...

Hi Distutils-SIG Folks,

If this is not the best place for a ‘pip’ question, please direct me to a better destination.

I have several virtual environments. As far as I know they should all be about the same WRT the python binary that was used to create them (home-brew python2.7.11/OSX). However they have different behavior WRT pip install. I’m trying to track down the cues that pip uses to choose a binary wheel, or a source/build install. I’ve been using ‘pip -v’ to get some hints, but it’s still not clear. I’ve saved two log files that illustrate the issue:

https://dl.dropboxusercontent.com/u/20562746/pydev_pip_log.txt

https://dl.dropboxusercontent.com/u/20562746/pytest_pip_log.txt

So my question is: How can I determine why pip is choosing ‘wheel’ in some cases and ‘source’ in others when I have the same python build in both cases?

thanks! -steve

_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig