Pyunit drives me nuts, I tell you
I've drunk of the test-first kool aid, and almost always try to write
some kind of pyunit test before writing any python code. Mostly this
works out just great, but it never ceases to amaze me that some simple
errors in the unit tests, such as a messed-up import statement, get
transparently swallowed. Someday I really ought to take a look at why
that is and how it can be fixed.
[/code]
Building psycopg is hard
I've gone through this dance a few times now over the last year, and it always trips me up at one point or the other. So, for future reference, here's one way to configure psycopg:
Note that this is with postgres 8; with earlier versions, there were some extra hoops to jump through for all the pg headers.
[/code]
I've gone through this dance a few times now over the last year, and it always trips me up at one point or the other. So, for future reference, here's one way to configure psycopg:
./configure \ --with-mxdatetime-includes=../egenix-mx-base-2.0.6/mx/DateTime/mxDateTime \ --with-postgres-includes=/usr/local/pgsql/include \ --with-postgres-libraries=/usr/local/pgsql/liband then make && make install. If you're planning to use this in Zope, also add:
--with-zope=/zope/myapp/ \ --with-python=/zope/myapp/bin/python \ --with-python-version=2.3and after make install, add make install-zope.
Note that this is with postgres 8; with earlier versions, there were some extra hoops to jump through for all the pg headers.
[/code]
slag code: