While working on a project using PyAMF today, i was about to write a unittest of a service method, when I realized that it would be harder than necessary to make unittests of the service. The cause of this is, that there was no test client wrapper for the django test client for pyamf, which means, that to do a unittest of the gateway, you’ll have to start a django server, and run a unittest elsewhere.
Seeing as how there are a lot of benefits to using djangos own test suite (fixtures and automatic database generation to name a few), i set out to write a little test client for PyAMF to utilize django’s test client, so it would be possible to write a proper test suite.
This turned out great, and is now ticket 508 over at PyAMFs trac. Look at the client.py for the code. At some point, it will be integrated into PyAMF mainline as
p.r.c.django.TestClient (or something like that).
It took me a while of messing with fontsets and various other settings, before i came across how to select fonts in the Emacs wiki:
- M-x mac-font-panel-mode and pick the font you want.
- M-x describe-font and copy the font name (e.g.
- Add the following to your
In my case the lines for font selection looks like this:
(set-face-font 'default "-apple-proggytiny-medium-r-normal--11-110-72-72-m-110-iso10646-1")
Using this to make the font display without antialisaing:
defaults write org.gnu.Emacs AppleAntiAliasingThreshold 100
And this to position emacs in the top left, and be 104 chars wide, and 64 high.
(setq initial-frame-alist `((width . 106) (height . 64)
(top . 0) (left . 0)))
And of course some other tweaks. Re-learning emacs is turning out to be a good idea. But that’s another story.