$ uname -r
A guide for reviewing code and having your code reviewed.
Peer code reviews are the single biggest thing you can do to improve your code - Jeff Atwood
Code review is an important part of a team's development process. It helps to:
- disseminate knowledge about the codebase/technology/techniques across teams
- increase awareness of the features being developed
local _M = {} | |
function _M.getHostname() | |
local f = io.popen ("/bin/hostname") | |
local hostname = f:read("*a") or "" | |
f:close() | |
hostname =string.gsub(hostname, "\n$", "") | |
return hostname | |
end | |
return _M |
import re | |
diff_re = re.compile( | |
"@@ \-(?P<removed_start>\d+),(?P<removed_length>\d+) " | |
"\+(?P<added_start>\d+),(?P<added_length>\d+) @@" | |
) | |
class DiffContext: |
FilteredCollection events are not granular: 'load', 'reset', 'filter-complete', and 'loaded' always trigger in sequence, and usually in duplicate, so there's no way to determine when to safely take a rendering action based on collection lifecycle events.
'sort' events are repeated many times on FilteredCollections--ideally sort events should be silent unless a change has actually occured. Binding rendering actions on 'sort' isn't possible because of all the duplicate events.
There are only a few events that I feel should be taking place in the lifecycle of a given FilteredCollection:
from tox._config import parseconfig | |
print "language: python" | |
print "python: 2.7" | |
print "env:" | |
for env in parseconfig(None, 'tox').envlist: | |
print " - TOX_ENV=%s" % env | |
print "install:" | |
print " - pip install tox" | |
print "script:" |
#!/bin/sh | |
SESSION_NAME="big_red" | |
cd ~/Sites/within3/big_red | |
tmux has-session -t ${SESSION_NAME} | |
if [ $? != 0 ] | |
then |
;;; python-pylint.el --- minor mode for running `pylint' | |
;; Copyright (c) 2009, 2010 Ian Eure <[email protected]> | |
;; Author: Ian Eure <[email protected]> | |
;; Keywords: languages python | |
;; Last edit: 2010-02-12 | |
;; Version: 1.01 |