As I learned from Announcement of PyConJP 2015, it seems that pip after 7.0 has prioritized wheel over sdist when installing the library. (Reference: pip release notes) http://pip.readthedocs.org/en/stable/news/
When I tried it, some of the packages (ex. IPython) that I used to install with sdist are now installed with the wheel. I'm happy that this makes the creation time of the virtualenv environment very short.
In my environment shown in here, Virtualenv is installed by "pip (Python) installed via Homebrew". It seems that "pip installed via Homebrew" is used in the environment created by this Virtualenv, so I upgraded the version of pip for each Python.
pip(Homebrew)Upgrade
$ brew upgrade python python3
Sure, this raised the version of pip, but at the same time raised the minor version of Python (3.4-> 3.5), and I had a problem that vim referencing the dynamic library of 3.4 did not work.
If it is safe, I think it is better to use the hook function of Virtualenv and upgrade only the pip in the created Virtualenv environment.
~/.virtualenvs/postmkvirtualenv
...
#Also make sure to use the latest setuptools
pip install --upgrade setuptools
pip install --upgrade pip
...
Recommended Posts