python - AWS's Elastic Beanstalk not using my virtualenv: "No module named boto" -
I am trying to use the elastic beanstock of AWS, but when I eb start
If I run, then I get "Import error: A module named Bito can not run A VS for local repository head."
I am in the virtual environment of my Django project, I run Install Pip installed
and it was successful. I got the pp freeze & gt; Requirements.txt
, Add git requirements.txt
, and git commit -m 'bits added in requirements.txt'
, all successful then I open the python Found and got imported bits without any consequential errors. Finally, I went back to the
It looks like eb start command is not using my VirtualNV What should I do?
Well, this is a hack and an ugly, but it has worked.
Now, there is an error on the local machine, nothing to do with the remote.
I have been installed locally and I have tested another barebones approach for Virtual Enviv (My own reasons.)
1 Note that where the error is occurring - .git / AWSDevTools / aws / dev_tools.py
2 Run non-virtualenv dragon and
import bite print. File /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ Site-Packages / Boto / Init .pyc
3 Open on it and add it to the dev_tools.py on top:
Import sys.path.append ("/ opt / local / Library / frameworks / Python.framework / version / 2.7 / lib / python2.7 / site-packages ")
Since you are joining sys.path, you only W Import module if git aws.push has not found it in its stuff.
It just fixes the problem, except that it will be again on the next directory where you do go to an "eb init"
4 where you unzip CLI In my case:
$ cd ~ / bin / AWS-ElasticBeanstalk-CLI-2.6.1
Now
5 of dev_tools.py See EB init
$ find ~ / bin -name dev_tools.py ~ / bin / AWS-ElasticBeanstalk-CLI-2.6.1 / AWSDevTools / Linux / scripts / aws / dev_tools.py
Edit this file as # 3
If you input Ebb elsewhere Not you see that your ugly hack there.
Not good, but it works.
Sorry for ps formatting, the newbie is here, it's late and I want to skate.
Comments
Post a Comment