> Django : very strong integration, excellent documentation and support,
> huge community, really easy to get started with. And possibly a bit more
> mature and stable...
One strong point in favour of Django: it follows Python's philosophy of
"batteries included", and features a large array of plugins. There are also
numerous other add-ons created by the community.
Also, it has a pretty great administration interface.
It still manages to retain flexibility, but you're basically stuck with
Django's ORM (which is OK for simple things) and templating language (which is
OK as long as you don't need custom tags).
> Pylons : more loosely coupled (imply: less integration), based on
> "standard" components - which is both a blessing and a curse, specially
> wrt/ documentation -, requires a good knowledge of Python and the HTTP
> protocol to get started with. Very powerful and flexible but this comes
> with a price...
Haven't used Pylons, but the documentation has improved the last few years
with the Pylons book (http://pylonsbook.com/en/1.0/), while still not being up
to par with Django's. It has also a methodology for deployment, which Django
decidedly lacks.
Cheers,
Emm