I am afraid that in practice I have always ended up going the simple "litter the code with print statements" route when debugging my Python. Without the compilation step, the cost of inserting and then removing these lines from the source code is relatively cheap, and has served me well enough so far.
SGE, be default, will happily oversubscribe processors when multiple queues target the same nodes (nice one, SGE).
Furthermore, even if jobs specify a memory limit, if each individual job uses less then the total memory limit, but the sum memory usage of jobs assigned to the machine exceeds the machine's memory, the memory of the entire node can be exhausted, sending it off into limbo (cunning, SGE, very cunning).
The solution to both of these issues is to specify processors and memory as consumable resources at the host level.
This post details the procedure.
Git offers two ways of viewing differences between commits, or between commits and your working tree: diff and difftool.
The first of these, by default, dumps the results to the standard output.
This mode of presentation is great for quick summaries of small sets of changes, but is a little cumbersome if there are a large number of changes between the two commits being compared and/or you want to closely examin
A standard dictum amongst experienced Vim users is not to use the arrow keys to move around your document.
This dictum is often repeated again and again, in tones that range from the taken-for-granted to hysterical-zeal.
The most common reason given for this is that using the arrow keys takes your hands away from the home row of your keyboard, and thus is wasteful both in terms of time and energy, whereas the standard Vim movement keys --- `h`, `j`, `k`, and `l` --- keep your hands on the home row, and therefore is far more efficient.
Here is what I have discovered: this anti-arrow key argument is wrong!
Vim's regular expression dialect is distinct from many of the other more popular ones out there today (and actually predates them).
One of the dialect differences that always leaves me fumbling has to do with which special characters need to be escaped.
Vim does have a special "very magic" mode (that is activated by "\v" in the regular expression) that makes thing very clean and simple in this regard: only letters, numbers and underscores are treated a