Hi, I took a look at Django when deciding what framework to use. Compared to TG, at a first look Django feels more polished - the documentation in particular is excellent. It's auto admin system is great, particularly because it is configurable. The problem I found with Django was that if you wanted to do something that doesn't quite fit its approach, you're back to doing things the long-hand way. It doesn't have the whole widgets/validators system that TG has, although they are working on this with "newforms". The Django ORM is nice for simple operations, but doesn't have the power of SQLObject (e.g. there is no SQLBuilder equivalent). The Django controller is more flexible, being based on regular expressions, but I find CherryPy's syntax is preferable for my work. So, all things considered, I decided to use TG and my decision is reinforced the more I learn.
Many people (including Guido) have commented that it would be great to combine the efforts of the projects, to produce one "hyper framework". I'd say in the short term, merging TG and Pylons is a more likely prospect, but perhaps Django could be brought closer. I believe ToscaWidgets already contains pretty much all the functionality of the Django "widgets" in newforms. If Django started using TW, we would have the beginnings of a meeting of minds. Fastdata2 could then be modelled after (or even replaced by) Django's auto-admin system. All the project already seem to be moving towards SQLAlchemy as the ORM. The controller is a harder one to merge - the regex/expose mechanisms will just suit different people. But perhaps the controller will become as pluggable as the template engine currently is. If all this happened, Django would effectively just be TG, using a particular choice of controller and templating engine. Frameworks are becoming more like distributions every day... Paul Randall wrote: >It's nice to see TurboGears finally pass the 1.0 milestone. About the >same time TurboGears started gathering steam, several other frameworks >either started up or came to my attention in what looked like a Python >web framework revolution. I think it's been about a year since and it >would be nice to see where these frameworks stand today. A >comprehensive list is here: http://wiki.python.org/moin/WebFrameworks. > Looks like Django and Pylons (two that I've evaluated) are moving >along and nearing 1.0 status. Anyone have enough experience with these >other frameworks to say how they compare to TurboGears today? > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
