On 04/30/2015 12:28 AM, boB Stepp wrote:
The main danger as I see it is that if I am not careful, then the code on the dev environment could diverge from the state of code on my Windows PC, i.e., I forgot to do the scp part. But when I am actively working on a section of code I always insert a few print statements (Py 2.4!) to verify I am getting what I should when I test it out--even if I don't have an actual problem yet. And so far this has immediately revealed those few instances so far when I forgot to save to the dev machine (Usually when someone has interrupted my workflow, a near constant occurrence at work.).
Add an automatic file copy to the save-key definition in your editor. Then whenever you save the file locally, you'll also be copying it to the master location.
If that's too hard, or your editor can't support it, write a bash script that does an rsynch every 10 minutes.
rsynch does what scp does, but it works on whole directories, copying only those files that changed. And you can fine tune what "changed" means.
There are other, less resource intense approaches, but if one of these works, it'll be pretty painless to set up.
-- DaveA _______________________________________________ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: https://mail.python.org/mailman/listinfo/tutor
