Author Archives: Wolfgang Schnerring

Most of gocept is headed towards the German PyCon next week! We’re excited and look forward to meeting people, exchanging ideas and learning new things. We have prepared several talks to share some of the experiences we gained over the … Continue reading →

Our second meet/talk/barbecue event was last week, and we think it was even better than the first one. In the unconference part, these were the topics we talked about: Demo of batou, the deployment tool Django Sentry: centralized error-logging DRBD … Continue reading →

We invited developers and sysadmins to join us for talking shop and barbecuing last Friday. Even though several people had signed up and said they wanted to come, at first none of the guests seemed to arrive. But after an hour … Continue reading →

Just a quick note for profiling e.g. Zope views: class MyView(object):     def __call__(self):         result = {}         cProfile.runctx(‘result["x"] = super(Body, self).__call__()’,                         globals(), locals(), ‘/tmp/viewprofile’)         return result['x'] Even though “exec ‘result = super(…) in globals(), locals()’ works, … Continue reading →

A wrinkly part of buildout‘s design is that the PYTHONPATH is not easily available outside of scripts generated by buildout itself. I’ve been using the following workaround in some of my development tools for a while and found it quite … Continue reading →

zope.testbrowser is a valuable tool for integration tests. Historically,  the Zope community used to write quite a lot of doctests, but we at gocept have found them to be rather clumsy and too often yielding neither good tests nor good … Continue reading →

For integration tests it can be helpful to have a fake HTTP server whose behaviour the tests can control. All necessary building blocks are even included in Python standard library. However, the BaseHTTPServer is surprisingly hard to shut down properly, … Continue reading →

Suppose you’ve written a script to “fix something real quick” and unleashed it upon your live database. Five minutes later, you discover your script had a bug, and now you’ve wrecked quite a bit of production data. Ouch. You might … Continue reading →