On Tue, Nov 11, 2014 at 12:36 AM, Roy Smith <r...@panix.com> wrote: > Yes, exactly. When you deploy your application someplace, you need to > include all the things it depends on. In the simple case of a few > python files (say, a main program and a few modules that you're > written), the easiest thing to do might be to just clone your source > repository on the other machine and run it directly from that.
Even in less simple cases, that's often a good way to run things. As long as your source repo has no large binary files in it, it'll be reasonably small; for 400KB of source code and ~1600 commits spanning ~3 years of history, around about 2MB. When your deployment is a source clone, it's really easy to pull changes and see what's new; and if you ever find a bug on a deployment machine (maybe a different OS from your usual dev system), you can make a patch right there and send it along. There's no huge "okay, let's make a new release now" overhead - you just keep committing (maybe pushing) changes, same as you do any other time, and perhaps tag some commit with a version number. Very very easy. I recommend it. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
