Jake Melikov jake-melikov

Previous versions used homebrew to install the various versions. As suggested in the comments, it's better to use pyenv instead. If you are looking for the previous version of this document, see the revision history.

$ brew update
$ brew install pyenv
$ pyenv install 3.5.0
$ pyenv install 3.4.3
$ pyenv install 3.3.6
$ pyenv install 3.2.6
$ pyenv install 2.7.10

$ pyenv install 2.6.9

	# Pass the env-vars to MYCOMMAND
	eval $(egrep -v '^#' .env \| xargs) MYCOMMAND
	# … or ...
	# Export the vars in .env into your shell:
	export $(egrep -v '^#' .env \| xargs)

	# This is the nuclear option. Use with extreme care
	# Works up to and including Mountain Lion (10.8.x)

	# Show all extended attributes
	ls -lOe ~/dir-to-fix

	# Remove no-change attributes
	sudo chflags nouchg ~/dir-to-fix

	# Recursively clear all entended attributes

	var winston = require('winston'); // https://github.com/flatiron/winston

	var logger = new (winston.Logger)({
	transports: [
	new (winston.transports.Console)(),
	new (winston.transports.File)({ filename : 'winston.log', timestamp: true, /maxsize: 2000, maxFiles: 5/ })
	]
	});

	process.on('uncaughtException', function (err) {