June 2007 Archives
13 entries filed this month:
In part six of Python Web Application Diary we looked at data persistence
using Durus and wrote Sancho unit tests and a skeleton Pyblosxom migration
tool. Today we'll extend the basic UI created in part five for our Entry
object, and we'll create a base UI for the Journal object too. At that point
we'll be able to wire our new JournalDirectory into SiteDirectory (also
referenced in part five) - a QP application's "master controller" - which
will allow us to start publishing previously created journal entries to the
web. (1033 words) More …
The Senate is a philosophically-conservative institution intended to provide a check on the excesses of partisan elected politicians in the Commons, meaning particularly in the 21st century the Prime Minister and Cabinet. But that is lost on a government which sees as its ideal the executive power of a president and an Upper Chamber designed to jealously pursue the divisive parochial interests of state or provincial “rights”; indeed, “Canada’s New Government” patterns itself after 1776 not 1867. Brian Marlatt (170 words) More …
Overheard in question period: Government House Leader Peter Van Loan calling on the Liberals to “stand up for democracy,” this in reference to goings on in the Senate. (227 words) More …
Imagine a world where the most productive farmland (total output) in the world – North America – is a barren wasteland – and you’ll be imagining what this U.S. government report imagines will happen if we do not bring greenhouse gas emissions under control and effect reductions. (68 words) More …
The number one and two issues that come to mind are: (507 words) More …
In this installment of our web application diary we'll work more with the
Durus object database by injecting some data into it; exploring the
interactive interpreter (one of the cool features of Durus to be sure) and
starting the basis for a conversion script to take weblog data in PyBlosxom
format and insert it into our blog application database. (2447 words) More …
In part two we created file system hierarchies for both a library and our
project application. Since we plan on reusing our journal objects and related
UI, those components will live in our library and our application itself will
import them. (1856 words) More …
In other news, the sun also rose. (122 words) More …
Our object model so far is very simplistic; lets add a healthy dose of
constraints to aid both in testing and also prevent unintended (mis)use down
the road. (1182 words) More …
Today lets start writing code -- we'll begin by defining basic objects for
managing weblog or journal entries, and then we'll move on to showing how
QP and Durus make defining and publishing your Python objects as easy as,
well, py. (904 words) More …
I presented in part one some of the choices I've made for my own system
configuration as it pertains to file layouts and hierarchies. (440 words) More …
For all the relevant packages I copy or move the extracted tarball sources
into “/www/lib“ and have shortcuts in “vim“ that let me quickly find and
open the source. I’ve also got a collection of vim shortcuts which help speed
up the write and test cycle, including toggling back and forth between the
current module and its corresponding test suite which lives in
“./test/utest_module.py“. (205 words) More …