I’ve been using many different Python Web Frameworks so far:
All frameworks have its strengths and weakness. For new project that will handle appointments using existing calendar I decided to give web2py a try, rationale:
- all stuff included on board, no manual integration of 3rd party libraries
- stable API
- small and elegant
- integrates with GAE (with subset of DB layer)
- template selection separated from controller (easier unit testing)
- easy template syntax (reuses Python code embedded into markup language)
After first phase of product I’ll report if my expectations above were correct and what kind of problems were located (if any).
Changing database location is simple – just launch dump on source database server, import it into destination database, redirect domain and voila! You can use this method to migrate your database into newer database engine version. But what can you do if you realize whole backend must be changed (i.e. from MySQL to PostgreSQL)?
Migrating SQL dump to different database dialect is not very easy (column types / dates formats as first examples come to mind). But you don’t have to operate on SQL dumps. The simple answer here is: “dumpdata”.
New version (1.1) of very popular web framework Django has been released. New version includes ORM improvements, better testing performance, conditional view processing and URL namespaces.
One of SQLObject benefits over Django ORM was in my opinion possibility to make aggregations without issuing raw SQL-s. This feature is now present in Django allowing to make more efficient reports implementation.
A table can be marked now as “unmanaged“: syncdb/reset will not touch such table. Also: proxy models and deferred fields now are present.
Big optiomalisation for unit testing fans like me: tests are run in one transaction, so performance is much better than before. I don’t use Django unit test infrastructure (selected nosetests for this task), but it’s pleased to hear about this improvement. Hope it will make unit testing more popular among Django programmers.