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

Make sure virtualenv picks up Python 2.7 #13

Closed
zombietango opened this issue Mar 26, 2018 · 1 comment
Closed

Make sure virtualenv picks up Python 2.7 #13

zombietango opened this issue Mar 26, 2018 · 1 comment

Comments

@zombietango
Copy link

Just so others don't waste a day or so on this like I did - make sure that virtualenv is picking up your Python 2.7 environment and not your 3.X one. I'm setting this up on a system running macOS and that has multiple Python environments. Base 'virtualenv metta' was pulling my Brew installed Python 3.6 environment while it seems Metta either requires 2.7 or just doesn't like my 3.6 build.

Running:

virtualenv --python=<path to preferred python> metta

fixed the issue.

Recommendation - Make note in setup/README that Metta requires Python 2.7 (if this is indeed the case) or make note that if you are getting import errors on workers.vagranttasks or BaseConfig (which is where my problems were) you should declare a different Python environment when creating the virtualenv.

carnal0wnage added a commit that referenced this issue Mar 26, 2018
update readme per issue #13 #13
@carnal0wnage
Copy link
Contributor

sorry for the confusion. I've updated the setup doc. If this doesnt resolve it for others (in your opinion) please open another issue.

5280d3a

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

2 participants