On Oct 14, 6:54 am, Pete Heybrock <[email protected]>
wrote:
> My team at work are thinking of using Pylons to provide a GUI for an
> existing suite of command line utilites. Although I'm impressed with
> what it offers, I've found the learning curve pretty steep (my
> previous experience being with relatively simple Perl CGIs). Can
> anyone reassure me that the effort is worthwhile and that there is
> adequate community support available (compared to other frameworks
> such as Django etc.)

Between Django and Pylons, if documentation is what you're after,
Django wins that hands down versus almost any framework.  That being
said, there are things Django does that are different.  The learning
curve for both is steep if you are coming from a non-MVC background.
Moving from Perl to Python isn't too bad, but, moving from CGI to
Pylons will be a giant leap.

Form handling is handled differently in each.  In Django, the same
controller that handles the display of your template for data input is
the same controller than handles processing the data and updating the
database.  If you like this, and go with Pylons, django-forms has been
ported: http://marcuscavanaugh.com/posts/pylons-django-forms/

If you need Authentication, Django's authentication system (which is
currently undergoing a rewrite) is very complete.  With Pylons, there
are some pretty good libraries as well.  Repoze.who and Authkit
support is available.  Blastoff, http://pypi.python.org/pypi/BlastOff
includes almost everything that the Django base authentication system
has and is well written.

Djangosnippets.org has plenty of additional pieces of code for your
project.  Pylons has started: http://pylonshq.com/snippets

Both Pylons and Django are great pieces of software designed to handle
different tasks.  Django is more about publishing, Pylons is more
about web applications.  Either way you go, I think you'll find both
able to handle your needs.

If you are trying to do things that aren't already in the framework
you choose, I find it much easier to extend Pylons than Django.  If
you don't like some aspect of Pylons, it is fairly easy to replace
that portion with an alternative solution.  For example, if you don't
like authkit, you can use repoze.who.  Not a fan of Mako?  Use Genshi
or Jinja2.  If you aren't a fan of Django's default ORM, and want to
use their admin panel, you can't use SQLAlchemy.  Their ORM is highly
integrated into Django which is fine for their purposes.  I prefer
SQLAlchemy over Django's ORM.

In the long run, I think you'll be better served with Pylons than
Django.  Read through some of the archives of this list, post some
questions and give it a try.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" 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/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to