Can not install the same packages in different virtualenvs

[romabysen]

If I create two virtualenvs, say A and B, and use python::pip to install gunicorn in both it will fail with this error:
Error 400 on SERVER: Duplicate declaration: Python::Pip[gunicorn] is already declared in file [.....]

This somewhat defeats the purpose of virtualenvs and it would be really nice if the same package could be installed in more than one virtualenv.

[sysreq0]

I wholeheartedly second that. Any idea if this can be worked out?

[lextoumbourou]

Hey guys,

This appears to have been fixed in this commit. If you specify the package name as a parameter and name the declaration something unique like:

python::pip { 'gunicorn-myenv':
    pkgname   => 'gunicorn',
    virtualenv  => $venv_path,
    owner       => $owner,
    require     => Python::Virtualenv[$venv_path],
}

It should get around this problem.

Thanks to @aelse for pointing this out.

---

If you can't install the latest version, another hacky work around is to specify the package name like: gunicorn#some-random-string. Pip appears to ignore everything after the # and Puppet is fooled into thinking it's a unique declaration.