[Tutor] Python CMS advice wanted

[jim stockford]

    I'd love to know scott's definition of "framework", especially
contrasting with full-blown CMS.
    Frameworks for Python:
CherryPy · Django · Karrigell · Nevow · Porcupine · Pylons · Spyce · 
TurboGears · TwistedWeb · Webware · Zope
    per  http://en.wikipedia.org/wiki/Django_(web_framework)

    Richard, i think from the (very) little investigation i did
following scott's last post, that you should investigate
Django. to me it looks like a pretty streamlined "framework"
that marries a database (your choice of a few) to a web
server (apache seems their choice) via mod_python.
    there's a learning curve, but that seems an inevitable
hurdle: you only get to choose which, so do a little
window shopping.
    the example sites look streamlined. django presents
an object-oriented API to whatever database you hook
to.  mod_python ensures near-optimum performance.
    If you take a look on the top-level page for django
http://www.djangoproject.com/
you should see a link for "DRY principle". Click it and
read and follow the links in the subsequent pages:
you'll find an easy-to-read, to-the-point set of links to
coders' wisdom (Don't Repeat Yourself,
OnceAndOnlyOnce, YouAren'tGonnaNeedIt, and more).


http://www.djangoproject.com/


On Nov 27, 2007, at 6:49 PM, Richard Querin wrote:

> Whoa!. Lots of very good advice here. Thanks to all.
>
> After reading it all I'm wondering if maybe a templating system like
> Cheetah might be the way to go for us. I'll have to do a lot more
> reading and exploring. I'd love to learn something like Django but
> like it has been said, that's really a framework you'd use to build a
> CMS. And this site is really a labour of love and not a business
> venture so the time we invest into it at the moment is kind of in
> short supply.
>
> While we have less than 50 entries at the moment, adding each one is
> still quite a hack. I've written a small wxpython app to take away
> some of the pain of it, but it's still prone to corruption and still
> too much work.
>
> I think I'll have to watch some demo's to get a feel for how some of
> these systems work before going down any specific path, because a lot
> of it is still Greek to me.
>
> Again sincere thanks for all the great info, and I'll try to check
> back in on this thread once we get going on a solution.
>
> RQ
> _______________________________________________
> Tutor maillist  -  Tutor at python.org
> http://mail.python.org/mailman/listinfo/tutor
>