On Oct 12, 6:37 pm, m h <[email protected]> wrote: > Has anyone done something like this with Pylons? (ie have Pylons and > it's dependencies in SCM, rather than having to install them).
If they really want third-party packages to be in the SCM as well, you could put an entire virtualenv directory in the SCM. Use the --no-site- packages option to virtualenv to make it self-contained: virtualenv --no-site-packages $DIRNAME >From $DIRNAME, run "source ./bin/activate", then install things with easy_install or pip, then put in your app directories, then put it all in the SCM. If you use easy_install use the -Z option to prevent it from zipping anything. pip has zip/unzip commands. Make sure to use the python executable that's in $DIRNAME/bin rather than the system python. Jason --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
