On Oct 13, 12:04 pm, Mike Orr <[email protected]> wrote: > I would hesitate to put the entire virtualenv into version control > because the Python executable is a binary, there are symlinks from the > lib directory to the system Python, and also .so files (binary) in the > lib directory. These all will work only on the same computer, or at > least one with identical paths, OS, and Python version.
Good point! I haven't actually done this. But if you wanted the convenience of virtualenv installation on the client side, you could use an exclude list in the SCM (e.g. .git/info/exclude) to prevent any of the binaries from creeping in, then either overlap the deployment with a virtualenv on the server (to use its binary versions) or have no virtualenv on the server and set PYTHONPATH. (Mike's idea of pushing source tarballs to the server and installing them there sounds like it would work too.) The "pip bundle" command looks promising, but the docs still explicitly say it's not stable. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
