Need to specify pip version

[Peter Burkholder]

The default recipe used to install pip 1.4.1. After the upstream released 1.5 on 1/1

http://www.pip-installer.org/en/latest/news.html#id1

our new nodes don't converge because that requires a newer version of setuptools. I don't see any way in the cookbook to specify the pip version.

Can you add that, or show me what I'm missing? Thanks, P.

[Martin Cozzi]

+1 this is a problem for us too.

[Noah Kantrowitz]

I'm working with the PyPA team now.

[i-sam]

Have the same problem..

[christopherhan]

+1. Our nodes fail to converge when installing from requirements.txt:

Downloading/unpacking fcrypt==1.3.1 (from -r requirements.txt (line 26))
  Could not find any downloads that satisfy the requirement fcrypt==1.3.1 (from -r requirements.txt (line 26))
  Some externally hosted files were ignored (use --allow-external fcrypt to allow).
Cleaning up...
No distributions at all found for fcrypt==1.3.1 (from -r requirements.txt (line 26))
Storing debug log for failure in /path/to/shared/.pip/pip.log

Looks like pip 1.5 made a backwards incompatible change. From the 1.5 release notes:

pip no longer will scrape insecure external urls by default nor will it install externally hosted files by default. Users may opt into installing externally hosted or insecure files or urls using --allow-external PROJECT and --allow-unverified PROJECT.

For each package that fails to install from the requirements file, we can pass --allow-external and --allow-unverified to the install command. e.g.

pip install fcrypt==1.3.1 --allow-external fcrypt --allow-unverified fcrypt

[christopherhan]

@coderanger Any updates from the PyPA team on this?

[Noah Kantrowitz]

The plan is to remove the hard dependency between pip and setuptools for pip 1.5.1 which should be out soon.

[Kyle Gibson]

Couldn't you just use the new version of pip to install a previous version?

python_pip 'pip' do
    version '1.4.1'
end

[Peter Burkholder]

I think this can be closed.