Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pip resource requirements cause dependency cycle #509

Open
ruanda opened this issue Sep 24, 2019 · 0 comments
Open

pip resource requirements cause dependency cycle #509

ruanda opened this issue Sep 24, 2019 · 0 comments

Comments

@ruanda
Copy link

ruanda commented Sep 24, 2019

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: v5.5.14
  • Ruby: 2.4.5p335
  • Distribution: Centos 7
  • Module version: 2.2.3-rc0

How to reproduce (e.g Puppet code you use)

If you create venvs in two different modules which depend on each other and install packages via python::pip, dependency cycle appears as all venvs are requirements for each python::pip.

What behaviour did you expect instead

Python:;pip should depend only on venvs it uses.

Any additional information you'd like to impart

Affecting lines start at https://github.com/voxpupuli/puppet-python/blob/master/manifests/pip.pp#L75. Those collectors should probably limit venv by path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant