On Sun, Sep 20, 2009 at 6:57 PM, William Stein <wst...@gmail.com> wrote: > > On Sun, Sep 20, 2009 at 6:29 PM, Tim Joseph Dumol <t...@timdumol.com> wrote: >> On Mon, Sep 21, 2009 at 4:04 AM, Ondrej Certik <ond...@certik.cz> wrote: >>> >>> On Sun, Sep 20, 2009 at 6:22 AM, Tim Joseph Dumol <t...@timdumol.com> >>> wrote: >>> > <SNIP> >>> > That's excellent. I personally favor Pylons as well, but I thought >>> > Django is >>> > the more popular, and thus more hackable framework at the moment. I >>> > would >>> > love to see his code. >>> >>> Indeed, I know Django, so I know how to get things done in that. But I >>> don't know Pylons, so I would have to learn it first (which I am not >>> opposed to). >>> >>> Since you know both, could you please tell me the advantages of pylons >>> over django? I browsed through the pylons tutorials and documentation >>> and it seems to me it's just another framework, so one can do the same >>> things as in django, just differently, so that's annoying. Maybe there >>> is some conceptual difference? >>> >> >> Django is designed to be a monolithic framework -- the ORM, templating >> system, url routing, authentication, etc. are all from Django. Pylons is >> designed to be highly modular -- the ORM can be any of SQLObject, >> SQLAlchemy, or any other ORM you want, and the same goes for the rest. This >> makes it much easier to switch backends, templating systems, etc. It also >> makes moving out of the framework easier -- although that doesn't seem to be >> much of a problem. >> >> Also, Pylons based its MVC paradigm on Rails, while Django has an MTV >> (Model-Template-Controller) paradigm. >> >> Django was originally designed to be run from `mod_python`, while Pylons was >> designed from the ground up to run on WSGI. This means that it is much >> simpler to use WSGI middleware. Django, on the other hand, has its own >> non-standard middleware system. >> >> Pylons has pluggable solutions to Django's monolithic packages -- AuthKit >> for authentication, Jinja2/Mako/Genshi/... for templating, etc. >> >> That's as far as I can get from the top of my head. >> > > You just made Pylons sound (to me) better in every possible way to Django!
Indeed, it sounds better. The only reason why I still use django is that I know it works almost everywhere I need it (and it's not such a big deal to use different templates either, e.g. it's python, so I just import what I need), but I'll look at pylons in my free time and try to learn it too. Thanks for the info. Ondrej --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
