virtualenv doesn't seem to work with a path relative to home (~/), but while I put that in my email, I actually used a root relative path. It was activating the venv.
I have a feeling that you are not seeing the problem because you already have it all installed in your system. Are you running "python getsatchmo.py" with sudo in front? Try it without. Check ./lib/python2.5/site-packages inside your venv, are the packages there? So I managed to get it to work this is what I did: Hard coded a pip -E option into the script. Created and activated the venv Ran "python getsatchmo.py" twice. I had to run "python getsatchmo.py" twice because the first time it complained "ImportError: No module named satchmo_store" I will look into this further later this evening. Simon 2009/9/14 Chris Moffitt <[email protected]> > Simon, > > Thanks for the feedback. I'm not 100% sure that doing virtualenv > ~/venvs/satchmo enables the environment. I think you need to do a source > ./bin/activate in order to start using it. Give that a try first. I tested > in a virtual env and it does work if you have activated it. > > You do raise a good point and maybe we can add an option to do pip -E > virtual env. > > As far as the requirements.txt file, I will probably include it in the > future once we coalesce on the strategy. > > Thanks, > Chris > > > On Mon, Sep 14, 2009 at 3:35 AM, Simon <[email protected]> wrote: > >> This is a great step in the right direction. I believe Pinax has had some >> criticism/friction recently in regard to their installation but it was more >> related to what they include in their source tree. I think this is one >> reason why Pinax is a good project to follow and learn from - especially >> form a Satchmo point of view. >> >> I tried to use the script to install Satchmo into a venv but it tried to >> install it into my system python. These are the commands that I ran. >> >> virtualenv ~/venvs/satchmo <-- Creates and activates venv >> python getsatchmo.py >> >> Am I missing something? In your script you run "pip install %s", when >> installing into a venv we should change that to "pip -E venv install %s" >> >> I already use pip to install and deploy Satchmo. To do this I need to keep >> install and setup separate as when it comes to deploying I already have the >> project in a git repo that doesn't need things like satchmo_copy_static. At >> the moment I maintain a requirements.txt that makes installing Satchmo one >> command "pip -E venv install -r requirements.txt" It would be nice if >> Satchmo had a requirements.txt that I could include in my projects >> requirements.txt. Your install script could also use this requirements.txt. >> (http://www.satchmoproject.com/requirements.txt) Ian Bicking talks about >> this here http://blog.ianbicking.org/2008/12/16/using-pip-requirements/ >> >> Another thing to note is that pip uses hg fetch if there is a clone of the >> repo in the src folder. hg fetch is not enabled by default :( All you need >> to do is add: >> >> [extensions] >> fetch = >> >> to ~/.hgrc >> >> Right, nice work >> Simon >> >> 2009/9/13 Chris Moffitt <[email protected]> >> >> I intend to post some more information about Djangocon to the list in the >>> future. Until I get to that, there is one topic that I wanted to start >>> discussing and get some input. >>> >>> At Djangocon, there were plenty of folks that had good things to say >>> about Satchmo but the overwhelming feedback (I know this isn't new either) >>> is that the installation process was too daunting. After looking at how >>> Pinax does things and learning more about PIP and virtualenv, I decided to >>> hack something together to see what we could do. >>> >>> I've created a Satchmo bootstrapping script called getsatchmo.py. It is >>> meant to take a bare bones Python + pip install and give you a functioning >>> Satchmo store in 1 command - can't get any easier than that ;) After hacking >>> away on the plane ride home and some further work today, I've got something >>> that is a good start. I would like some feedback from this group on how it >>> performs in your situations. >>> >>> To test this out - >>> - Download the script from here - >>> http://bitbucket.org/chris1610/satchmo/raw/cb9014f34353/scripts/getsatchmo.py >>> - Place in a suitable subdirectory >>> - sudo python getsatchmo.py >>> >>> BOOM. Everything should get downloaded and placed and you should be able >>> to run the satchmo demo store. You will need to have Python and PIP ( >>> http://pypi.python.org/pypi/pip ) installed and working. I also >>> recommend that you install PIL using your distributions binaries. PIL seems >>> finicky if you try to compile yourself. >>> >>> If you already have Satchmo running, then I'd recommend using a >>> virtualenv to isolate things for testing. >>> >>> Anyway, I hope people will take a couple of minutes and play with this to >>> see if it makes that initial install easier. Once I get some feedback, I'll >>> incorporate into the official docs. >>> >>> Thanks, >>> Chris >>> >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
