Using Python's built-in defaultdict we can easily define a tree data structure:
def tree(): return defaultdict(tree)
That's it!
Using Python's built-in defaultdict we can easily define a tree data structure:
def tree(): return defaultdict(tree)
That's it!
<!-- | |
Copyright (c) 2012 Terrence Ryan | |
Permission is hereby granted, free of charge, to any person obtaining a copy of this | |
software and associated documentation files (the "Software"), to deal in the Software | |
without restriction, including without limitation the rights to use, copy, modify, | |
merge, publish, distribute, sublicense, and/or sell copies of the Software, and to | |
permit persons to whom the Software is furnished to do so, subject to the following | |
conditions: |
%!TEX TS-program = xelatex | |
\documentclass[12pt]{scrartcl} | |
% The declaration of the document class: | |
% The second line here, i.e. | |
% \documentclass[12pt]{scrartcl} | |
% is a standard LaTeX document class declaration: | |
% we say what kind of document we are making in curly brackets, | |
% and specify any options in square brackets. |
# Base dirs | |
SRC_DIR = src | |
TMP_DIR = tmp | |
DEV_DIR = dev | |
SRC_PUBLIC_DIR := $(SRC_DIR)/public | |
SRC_STYLES_DIR := $(SRC_DIR)/styles | |
SRC_SCRIPTS_DIR := $(SRC_DIR)/scripts | |
TMP_SCRIPTS_DIR := $(TMP_DIR)/scripts | |
DEV_PUBLIC_DIR := $(DEV_DIR)/public | |
DEV_STYLES_DIR := $(DEV_DIR)/styles |
" I don't remember exactly how to make it not spit out the actual command you are running. Meh. | |
nnoremap u :call system("say -v whisper 'balls'")<CR> |
In your Python package, you have:
__init__.py
that designates this as a Python packagemodule_a.py
, containing a function action_a()
that references an attribute (like a function or variable) in module_b.py
, andmodule_b.py
, containing a function action_b()
that references an attribute (like a function or variable) in module_a.py
.This situation can introduce a circular import error: module_a
attempts to import module_b
, but can't, because module_b
needs to import module_a
, which is in the process of being interpreted.
But, sometimes Python is magic, and code that looks like it should cause this circular import error works just fine!
Oops. They did it again.
It hit the market during the last few weeks. Last generation of Intel Atoms: CedarView (D2300, D2500, D2550, D2600, D2700) and Cedar Trail (N2600, N2700, N2800) SoCs integrate a PowerVR GPU from Imagination instead of the usual Intel GPU. If you remember the Poulsbo fiasco, it's the same. More or less.
An unsupported graphic card on Linux distributions, and which can't properly support a basic desktop environnment like Unity or Gnome 3.
To prevent this issue, Intel woke up MeeGo from the dead in last february [to add support for CedarView]
-- make psql really quiet while the next several commands are processed | |
\set QUIET 1 | |
-- a colorful prompt that displays, in order: | |
-- * hostname (green) | |
-- * port number (yellow) | |
-- * user (blue) | |
-- * database (purple) | |
-- in the format: host:port user@db# | |
\set PROMPT1 '%[%033[1;32m%]%M:%[%033[1;33m%]%> %[%033[1;34m%]%n@%[%033[1;35m%]%/%R%[%033[0m%]%# ' |