Jorge Yau codenameyau

The Magic of Maybe

Consider the following code

def do_some_stuff(x)
  try:
    val = f(x)
  except NameError, e:
    val = False
  return va;

	# http:#eslint.org/docs/rules/
	ecmaFeatures:
	binaryLiterals: false # enable binary literals
	blockBindings: false # enable let and const (aka block bindings)
	defaultParams: false # enable default function parameters
	forOf: false # enable for-of loops
	generators: false # enable generators
	objectLiteralComputedProperties: false # enable computed object literal property names
	objectLiteralDuplicateProperties: false # enable duplicate object literal properties in strict mode
	objectLiteralShorthandMethods: false # enable object literal shorthand methods

	// Just before switching jobs:
	// Add one of these.
	// Preferably into the same commit where you do a large merge.
	//
	// This started as a tweet with a joke of "C++ pro-tip: #define private public",
	// and then it quickly escalated into more and more evil suggestions.
	// I've tried to capture interesting suggestions here.
	//
	// Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_,
	// @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant,

	# I know dict's have `.get()`, this example was made to break if the key is not
	# there to show the use of multiple try/except's
	# Yes I know that having the except and else on 1 line each does not fit with PEP8 standards.
	# But when you have many of them it helps reduce the size of the file and is no harder to read

	data = {'some_key': 'key value'}
	key_data = None
	for _ in range(1):
	try:
	key_data = data['someKey']