Here's my problem (it's a conceptual one). Coming from the world of mod_php, each file can represent a page with no intervention. I was not able to achieve the same with mod_python when I tried, and for that matter, couldn't put the pieces together in a usable way.
Let me start simply: If I wanted to create a trivial site, (Home, About, Contact) with a header and footer included, in PHP, it would be done as such: each page (index.php, about.php, contact.php) includes the template bits (header.php, footer.php). Is this simplicity achievable using Python? And by "simplicity," I'm referring to simplicity in execution; not necessarily an identical approach. Thanks, Thomas On Dec 17, 4:25 am, Graham Dumpleton <graham.dumple...@gmail.com> wrote: > On Dec 17, 11:10 am, Дамјан Георгиевски <gdam...@gmail.com> wrote: > > > > I'm trying again because I'm stubborn. Maybe the fourth time will be > > > the charm... > > > > Are there any good tutorials out there for setting up Apache with > > > mod_python? > > > mod_python is depreceated, nobody uses it. > > usemod_wsgihttp://www.modwsgi.org/ > > The mod_python package is not deprecated, although it could be said to > be sleeping at the moment. You'll also probably still find that more > new people choose mod_python over mod_wsgi. This is because it has the > more obvious name to look for when Googling. It also has publisher and > PSP high level handler which are still attractive to many as they are > more lightweight and easier to get into than the large WSGI > frameworks. Finally, the Django folks still recommend in their > documentation to use mod_python. > > Anyway, if wanting to host a WSGI capable application, using mod_wsgi > would be the more obvious choice. If wanting to write your own > framework, or work at low level, basing it on WSGI rather than > mod_python specific APIs would certainly be a better long term > direction to take. > > Graham -- http://mail.python.org/mailman/listinfo/python-list
