Getting back into Camp spirit, we (as in Gašper Ž. and I) thought about doing something for our growing Django community. Since a lot of things that we built runs on Django it feels just right.
What: Django (python framework thingie) community driven unconference for people that are already using Django. It’s not that we don’t like newbie’s, but we’ll invite them to event that is more optimized for them.
Where and when: Kiberpipa, Ljubljana on Saturday, 11th of December 2010
Language of event: Slovenian but you can present in English or Croatian
We plan to limit event to 40-50 people so it doesn’t get complicated with budget and organization. For the same reasons we probably won’t be recording the sessions, so that we can have group discussions and fingers pointing toward laptop displays.
Extra rule is that every participant should prepare a short presentation on something Django related. It can be a full-blown sessions tutorial, GIS Django example project or just a clever middleware hack.
Still interested in attending? Leave your e-mail in this quick form and we’ll keep you updated.
Debugging email sending in your Web application is always tricky as you need a working SMTP and you also need to watch out that you don’t accidently spam real users (if you’re working on a local copy of real database).
There is a neat one liner that acts as a “sink smtpd” server, meaning that it implements SMTP protocol, so you app can communicate with it, while printing everything it receives on screen:
sudo /usr/lib/python2.6/smtpd.py -n -c DebuggingServer localhost:25
(via Django Snippets)
I’ve been working intensively with Django for last few weeks and even managed to find a few bugs in it and also create a patch or two. Django-unicode branch is working very well for me and I would recommend using it as your main development branch since it solves a lot of problems if you are using unicode data (which often an issue for Slovenian developers).
Just a quick note to the few of you who are also tracking Django trunk. Today Django team changed clean_data in newforms to cleaned_data because of possible namespace clash. To port the new version you will just need to do some find and replace.
More important implication of this change is that now 0.96 newforms code is incompatible with Django trunk.
More about this in Django wiki