So you want to use Django, but you don’t want to use Apache and mod_python? DjangoCerise is a wrapper that lets you use CherryPy and WSGI instead.

O’Reilly Radar claims PyCon was a hiring fest and makes this comment:

This information is consistent with our analysis of the online book and job markets. Ruby has more momentum among startups, but Python is also a hot startup language, and is becoming one of the officially sanctioned licenses at many larger companies.

Interesting. I wonder if it’s true.

Jacob Kaplan-Moss has slides and notes from his Django tutorial, as well as some random quotes overheard at PyCon.

Whoa… they are saying Wordpress 2.1.1 is dangerous:

Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately.

Good thing I never bothered to upgrade. :)

I’ve been using Microsoft Outlook to manage my TODO list for a while.

Yes, I know… everyone complains about Outlook, but for me it fits the bill about 90% of the time. The tasks are easy to add, there’s a place to add notes, and it keeps track of when I complete tasks. But it is very limited in overall functionality, and it doesn’t scale well… with lots of old completed tasks cluttering the UI after a while.

I’m a picky person, and it’s just not quite right. So the hunt begins for the perfect TODO list…

(more…)

So I was playing with a small Django application the other night (a weblog, if you care) and found that I was unable to connect to the development server.

Firefox would tell me:

The connection was interrupted
The connection to 192.168.1.4:8000 was interrupted while the page was loading.

And the development server would report the following error:

AttributeError: WSGIRequestHandler instance has no attribute ‘path’

What was the problem? Heh, it was me being stupid.

It turns out I was accidentally typing https://192.168.1.4:8000 instead of http://192.168.1.4. I’m used to using SSL for connecting to my home server and I guess I did that by accident when connecting to the Django runserver.

So if you get that error, check to make sure you aren’t accidentally trying to use SSL.

Or at least that’s what one person (troll?) claimed on the pygame-users mailing list recently.

Personally I think the first reply was the best. :)