Archive 10/2008

Yesterday morning Nick Anderson contacted me and asked if I had an English version of my slides about using Buildout for Django-development that I made for a presentation at the Barcamp in Munich 2 weeks ago. I had totally forgotten about that. Originally I wanted to provide them in German and English but for some reason never did it. So here is now the English version of the slides. Enjoy

Sorry for the delay.

If you've ever had to work with some OWL-ontologies, you have definitely heard the name Pellet. It is perhaps the most wildly use opensource OWL-reasoner/engine out there. Yesterday Evren Sirin announced the release of the first release candidate of the upcoming version 2.0, that (among other things) includes preliminary support for OWL 2.0. But there is also a catch ...

Ever since I first heard the term "Photoblog" I always considered it a cool idea but definitely more something for other people ... basically those that get out more, have a life and whatnot. A couple of days ago I stumbled thanks to schokodinatorin upon Project365, a group on Flickr that has as a goal that you upload one picture every day to document your life. Naturally this is totally option, but I kind of like the idea of having one photo for each day of a year.

Today I released something I've planned to write for quite some time now: A very minimal recipe for zc.buildout that can install an arbitrary source distribution of a Python package. Sure, there is already collective.recipe.distutils out there and big kudos to Kevin Teague for his work there, but I had some minor problems with it. I also wanted to get some more practice when it comes to writing recipes for buildout. As always, you can find the result on PyPI and github.

Am Sonntag wollte ich beim Barcamp München eine kurze Einführung zu Buildout als Entwicklungs- und Deployment-Hilfe für Django-Projekte geben. Auch wenn keiner gekommen ist, hier nun die Folien.

Sie beschreiben kurz, wie man mit Buildout ein Django-Projekt verwaltet und auch ein entsprechendes WSGI-Script erstellt, ohne zusätzliche Biliotheken in den globalen PYTHONPATH installieren zu müssen.

Und wieder ein Barcamp erlebt Diesmal an der Reihe war das diesjährige Barcamp München, das mit Abstand größte Barcamp an dem ich jemals teilgenommen habe. Bis zum Schluss waren 215 Neulinge und 197 alte Hasen angemeldet. Keine Ahnung, ob wirklich so viele Leute da waren ... aber es waren seeeehr viele

Just a small plug for a project I'm currently working on. I'm playing a little bit around with zc.buildout right now and have come to a point where I want to have dependencies not only as subversion-repository, distutils or egg. I simply end up with too many Python packages on github for not having a way to use them. So while still learning my way around buildout I wrote a little recipe to do just that: clone a git-repo and make it accessible as a part. With this you can define first of all where the repository is, and also what branch or explicit revision you want to have for your project.

There is definitely still a ton of stuff missing that you'd find in any other zc.buildout recipe, but I see this mostly as a good way to finally find my way around Anyway, you can find it on the PyPI with a source package and an egg for Python 2.6. The code is also available on github.com.

Normalerweise bin ich ja nicht so der Museumgeher (und noch viel weniger wenn es um Kunst geht), aber wenn einem einmal im Rahmen der Langen Nacht der Museen nahezu alle Museen der Stadt um nur 11 EUR offen stehen, kann selbst ich nicht nein-sagen. Vor allem wenn es mit einem Photowalk kombiniert wird Alles in Allem war das ein sehr unterhaltsamer Abend; man hat schließlich nicht alle Tage Gelegenheit, Minimundus bei Nacht oder allgemein Museen bis oben hin gefüllt zu sehen.

As you might have guessed based on the recent activity in django-zsutils, this project is more or less a dumping ground for some ideas I have and snippets I use on multiple sites (or at least see myself using on multiple sites). The new step for any of these is, whether I can see them as standalone library. If I do, I try to clean them up even more and split them of the main package.

This happened yesterday to my little object-oriented views-implementation for Django. If you don't know this library yet, please take a look at its README or this blog post. Basically, the idea is to be able to share some common functionality between views by making views out of Python classes.

Today I did some final cleanup, moved it over to setuptools and finally made an actual 0.2.0 release including PyPI-registration, files etc. So if you want to use it, just run easy_install django-oopviews

I also registered the project on launchpad.net, so if you find any bugs or have some feature request or other questions, please ask there