seems to work fine Yes, there is a great piece of code called NPM for exactly this: https://npmjs.org/ You specify dependent packages in a package.json file (see the docs for syntax) and you can use npm install . to pull them in all at once, and then require them from your script.
fixed the issue. Will look into that further You have two issues here. One is the permissions issue as mentioned by @garnertb. pip tries to install in the site packages of the Python install which is owned by root. The other issue is that you are installing into Apple's python 2.7 and you say you want python 3.3. enter link description hereThe reason for this is that easy_install includes n its text the directory of the python that it comes from. Just typing easy_install gets you the first on the path which in this case looks like /usr/bin/easy_install which is the Apple installed one. you get the easy_install for python 3.3 you have to give its full path which depends on how you installed python 3.3
$ curl -O https://pypi.python.org/packages/source/v/virtualenv/virtualenv-X.X.tar.gz
$ tar xvfz virtualenv-X.X.tar.gz
$ cd virtualenv-X.X
$ [sudo] python setup.py install
I think the issue was by ths following , A popular convention is to list requirements in a text file (requirements.txt) and install them when deploying the project. Depending on your deployment configuration, libraries can be installed in a virtual environment (google keyword: virtualenv), or in a local user folder (pip install --user -r requirements.txt, if this is the only project under this account) or globally (pip install -r requirements.txt, e.g. in a docker container)