In article <c59fba7e-df71-4429-919b-cf34668fe...@s10g2000pbc.googlegroups.com>, Bryan <bryanjugglercryptograp...@yahoo.com> wrote:
> Django has emphasized backwards compatibility with the > down-side that, last I heard, there was no plan to move to Python 3. Hardly. See https://www.djangoproject.com/weblog/2012/mar/13/py3k/ I agree that Django is probably what the OP should be looking at, for most of the reasons you mention. The ecosystem/community which has grown up around Django is a major plus. I've done a couple of projects in Django, ranging from a fairly simple site based on django-cms, to a REST API server with a MongoDB back end. This later site actually used very little of Django's capabilities. I'm using the url routing, middleware framework, and session management, and that's about it. No templates, no ORM (at least not the one that comes with Django). But even with just using those small pieces, there was enough value in the scaffolding I got from Django to make it a good pick. -- http://mail.python.org/mailman/listinfo/python-list
