The methodology I've been using is that python packages that include native object files stay site wide. Python packages that are pure python generally go into one or more virtualenvs. I then skip the -- no-site-packages parameter when creating the virtualenv. But I never have a need for two different versions of something like python-mysqldb or two versions of PIL. I also have the headache that setting up a build environment on AIX is a PITA, so I avoid building packages that include native object files as much as possible.
However, you can also try dropping some strategic symlinks in $VIRTENV/ lib/python$PYVER/site-packages. Unfortunately, I haven't tried this for lib-dynload modules. And worst comes to worst and you aren't trying to mix python 2.5, virtualenv, and ssl... track down the build requirements and let pip or easy_install do the heavy lifting for you. On Nov 4, 11:26 am, Gary b <[email protected]> wrote: > Hello - I am having trouble figuring out how to use a MySQL db in a > django/satchmo project that exists in a virtualenv. > > Following the install method described > herehttp://www.satchmoproject.com/blog/2010/aug/01/satchmo-virtualenv/the > virtualenv is created without system default site-packages, which is > where my MySQL lives. > > Is the solution here as simple as making the virtualenv without the -- > no-site-packages qualifier? Or how would I go about installing MySQLdb > into my store virtualenv exactly? Can't seem to find the correct info > to do that...yet. -- 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.
