Aleck Landgraf alecklandgraf

Title

<Additional information about your API call. Try to use verbs that match both request type (fetching vs modifying) and plurality (one vs multiple).>

URL

<The URL Structure (path only, no root url)>
Method:

The Best of the Best Practices (BOBP) Guide for Python

A "Best of the Best Practices" (BOBP) guide to developing in Python.

In General

Values

"Build tools for others that you want to be built for you." - Kenneth Reitz
"Simplicity is alway better than functionality." - Pieter Hintjens

Hi Nicholas,

I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:

The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't

The point of this is to use cheap machines with small/slow storage to coordinate client requests while dedicating the machines with the big and fast storage to doing what they do best. I found that request coordination was contributing to about half the CPU usage on our Cassandra nodes, on average. Solid state storage is quite expensive, nearly doubling the cost of typical hardware. It also means that if people have control over hardware placement within the network, they can place proxy nodes closer to the client without impacting their storage footprint or fault tolerance characteristics.

This is accomplished in Cassandra by passing the -Dcassandra.join_ring=false option when the process is started. These nodes will connect to the seeds, cache the gossip data, load the schema, and begin listening for client requests. Messages like "/x.x.x.x is now UP!" will appear on the other nodes.

There are also some more practical benefits to this. Handling client requests caused us to push the NewSize of the heap up

	try:
	import xlrd

	def XLSDictReader(f, sheet_index=0):
	data = mmap.mmap(f.fileno(), 0, access=mmap.ACCESS_READ)
	book = xlrd.open_workbook(file_contents=data)
	sheet = book.sheet_by_index(sheet_index)

	def item(i, j):
	return (sheet.cell_value(0,j), sheet.cell_value(i,j))

	import sys
	import logging
	from optparse import make_option

	from django.core.management.base import BaseCommand, CommandError

	class Command(BaseCommand):
	help = ("Invalidates portions of the queryset cache based on the app names"
	" or models provided as arguments to the command. If no arguments "
	"are provided, nothing is done. To clear the entire queryset "

	<!DOCTYPE html>
	<html>
	<head>
	<title>Chernoff Smileys</title>
	<script type="text/javascript" src="http://mbostock.github.com/d3/d3.js?2.5.0"></script>
	<script type="text/javascript" src="http://mbostock.github.com/d3/d3.layout.js?2.5.0"></script>
	<style type="text/css">

	</style>
	</head>

	description "uWSGI server for electris CMS"

	start on runlevel [2345] # start on all runlevels.
	stop on runlevel [!2345] # stop when shutting down.

	respawn # respawn if job crashes or is stopped ungracefully.
	env DEPLOYMENT_TARGET=production # set any environment variables you like here.
	env DJANGO_SETTINGS_FILE=conf/settings.py # more environment variables if you like.
	env PYTHONPATH=/home/ubuntu/apps/my_app:/home/ubuntu/.virtualenv/my_app

	#!/bin/sh
	# Just copy and paste the lines below (all at once, it won't work line by line!)
	# MAKE SURE YOU ARE HAPPY WITH WHAT IT DOES FIRST! THERE IS NO WARRANTY!

	function abort {
	echo "$1"
	exit 1
	}

	set -e

	height: 650
	license: mit