Skip to content

Instantly share code, notes, and snippets.

Just over halfway through the flight, all the coffee in my stomach feels like it's percolating its way down into my lower intestine. I hunker down and try and focus on other things. What feels like an hour, but probably isn't more than twenty minutes, passes. We then enter what turns out to be pretty violent turbulence. With each bounce, I have to fight my body, trying not to shit my pants. "Thirty minutes to landing, maybe forty five" I try and tell myself, each jostle a gamble I can't afford to lose. I signal to [the flight attendant] and she heads toward me.
"Excuse me, where is the bathroom, because I don't see a door?" I ask while still devoting considerable energy to fighting off what starts to feel like someone shook a seltzer bottle and shoved it up my ass. She looks at me, bemused, and says, "Well, we don't really have one per se." She continues, "Technically, we have one, but it's really just for emergencies. Don't worry, we're landing shortly anyway."
"I'm pretty sure this qualifies as an emergen
# Add auto-completion and a stored history file of commands to your Python
# interactive interpreter. Requires Python 2.0+, readline. Autocomplete is
# bound to the Esc key by default (you can change it - see readline docs).
#
# Store the file in ~/.python_startup, and set an environment variable to point
# to it: "export PYTHONSTARTUP=$HOME/.python_startup" in bash.
#
# Note that PYTHONSTARTUP does *not* expand "~", so you have to put in the
# full path to your home directory.
Python 2.7.2 (default, Oct 11 2012, 20:14:37)
[GCC 4.2.1 Compatible Apple Clang 4.0 (tags/Apple/clang-418.0.60)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> class Thing(object):
... pass
...
>>> x = Thing()
>>> setattr(x, ' ', True)
>>> setattr(x, '+', True)
>>> setattr(x, '', True)
@waptang
waptang / normal-output.log
Created March 28, 2013 21:59
What seems to be a bug in CFEngine when using useresult/bundle_return_value_index. It appears that in some situations, the called bundles fail unless there is an additional output in the results section of the called bundle. The only difference between the bad_result and good_result bundles is that good_result has "input: $(input)" in the report…
R: input: test_result.data[alpha]
R: good: ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz