Pip not happy about version number mismatch when installing, bails out.

Issue #51 resolved
Christian Hudon created an issue

Hi,

It's currently impossible to install a specific version of rpy2 via a pip requirements file. When trying to install with a requirement line of "rpy2==2.1.3":

Downloading/unpacking rpy2==2.1.3 (from -r requirements.txt (line 3)) Downloading rpy2-2.1.3.tar.gz (127Kb): 127Kb downloaded Running setup.py egg_info for package rpy2 Source in ./build/rpy2 has the version 2.1.3dev-20100622, which does not match the requirement rpy2==2.1.3 (from -r requirements.txt (line 3)) Source in ./build/rpy2 has version 2.1.3dev-20100622 that conflicts with rpy2==2.1.3 (from -r requirements.txt (line 3))

When trying to install with a requirement line of "rpy2==2.1.3dev-20100622"

2.1.3dev-20100622 (from -r requirements.txt (line 3)) Could not find a version that satisfies the requirement rpy2==2.1.3dev-20100622 (from -r requirements.txt (line 3)) (from versions: ) No distributions matching the version for rpy2==2.1.3dev-20100622 (from -r requirements.txt (line 3))

From what I can tell, the problem is that the version passed to the disutils.setup() function (2.1.3) and the version in the egg-info PKG-INFO (2.1.3dev-20100622) do not match. Would it be possible to make both say (at least for the next bugfix release) "2.1.4" (without the "dev" and date suffixes)?

Thanks!

Christian

Comments (3)

  1. Laurent Gautier
    • changed status to open
    • changed milestone to 2.1.4

    Yes, I noticed that some time ago, but hoped it would not be a major annoyance to anyone. I confess having struggled a bit with the twists and turns present in distutils, setuptools, and Distribute, and was happy not touching it anymore.

    Do you think you could contribute a patch ? It would then definitely be part of 2.1.4 (and I'll port it to 2.2.0-dev).

  2. Laurent Gautier

    In the absence of further specifications, I commented "dev=true" out in setup.cfg. May be it will help. In the meanwhile this is considered resolved.

  3. Log in to comment