More of a story than anything. I'm not sure if this is typical for someone going from PHP to Python, but it might give you an idea of what to expect if you end

More of a story than anything. I'm not sure if this is typical for someone going from PHP to Python, but it might give you an idea of what to expect if you end up becoming a Python convert. I went from PHP-Nuke, to pure PHP, to Python, to handwritten Python site engines, to Google App Engine, and now finally hunkering down and getting Django under my belt, for real this time. And that's my first tip: GAE makes a great stepping stone to Django (and even includes a sizable chunk of Django). I have a very bad taste in my mouth from prior experience with Joomla, but I found Drupal to be very easy to use. But once I made the decision to finally learn a real framework, Python and Django made the work... almost trivial. Looking at the code for Drupal modules now makes me wonder why I let myself do all of that extra work that Django doesn't require. I'm with jacquesm, I still use PHP from time to time for minor things, simply because there are a good amount of hosting providers that don't offer Django. But I think my experience with Python has made me a better PHP programmer. However that works. However I've never really had issues with forms, at least not with GAE, but it IS a little wonky. self.request.get('form_field_name')