There are two kinds of fast in programming: Fast to code and fast to run. 3D applications and games are known to be speedy. But the time it takes to write and understand the code behind it? Not so much. On the flipside, many abstraction layers designed to make coding easier usually aren’t very efficient. So where’s the median? Meet Pyglet for Python.

Applications can create a lot of temporary files sometimes, and these files aren’t always cleaned up automatically. An example of this is when you run Python applications. Particularly if you’re a Python developer, your source code directories stack up with a .pyc version of each file, which is the cached compiled copy of the script.

"Git has sometimes been described as a versioning file-system which happens to support the underlying notions of version control. And while most people do simply use Git as a version control system, it remains true that it can be used for other tasks as well.

"Some Useful Emacs Python Mode commands..." -- GNU Emacs Manual: http://www.gnu.org/doc/emacs16.html

"I had some problems finding out a good Emacs setup for Python programmers, so I hope this will be useful to somebody. Requirements: ..."

This web log entry notes the ongoing software liberation process of Scott Carpenter. Scott is still currently dependant upon some non-free programs but is learning of the ways of living in liberty.

"As I mentioned in my previous post, I'm in the process of evaluating the core infrastructure for a massively multiplayer on-line game (MMOG). The current technology contenders for the server are Stackless Python (and it's eventual successor PyPy) or Erlang..."

"This is partially in response to Chris', Why Python 3k Shouldn’t Be Ruby (and a mention of Erlang) and my investigation on what I see Python 3000 as being, in plain English..."