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.

Sign up for GitHub

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

Jump to bottom

virtualenv does not use SCL path from environment #212

Closed
seblau opened this issue Jul 14, 2015 · 2 comments
Closed

virtualenv does not use SCL path from environment #212

seblau opened this issue Jul 14, 2015 · 2 comments
Assignees
@ghoneycutt

Comments

@seblau
Copy link

seblau commented Jul 14, 2015

We have to use a alternative python2.7 installation via RedHat SCL. Is there a possibility to specify the path of the python executable for python::virtualenv? virtualenv.py uses the PATH env variable to discover the python binary. Unfortunately exported paths via Exec do not affect the PATH within the puppet run.
@seblau
Copy link
Author

seblau commented Jul 15, 2015

The following path-option provided by python::virtualenv solved my problem. First just looked at the readme which is incomplete, completing the README.md would be helpful.

path
  • Specifies the PATH variable. Default: [ '/bin', '/usr/bin', '/usr/sbin' ]

@shivapoudel
Copy link
Contributor

@seblau done 48202f1

shivapoudel pushed a commit that referenced this issue Sep 1, 2015
Fix - Default PATH variable in readme for pyvenv
aac288a 
Closes #212
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ghoneycutt ghoneycutt

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ghoneycutt @shivapoudel @seblau