Using python on the web

spenrose at spenrose at
Thu Apr 20 19:12:58 EDT 2000

We build medium-busy, CGI-intensive sites in Python. We were briefly
quite excited about Zope, but once we realized it locked us into Yet
Another Programming Language, we lost interest. DHTML is particularly
problematic, AFAI can tell, because it doesn't appear to allow the
segregation of HTML development from coding the way Python string
substitution does. We hire very skilled HTML people to do HTML and tell
them to leave our sustitution tags alone, rather than taking the time
and money to create novice DHTML people to do the same work. If we were
going to learn another language for production purposes, Perl, Java, and
C++ all have vastly larger infrastructures (code bases, labor pools,
documentation, etc.) than DHTML ever will. There are enough hassles in
using Python, which I love, because of its relatively small installed
base. No way am I going to something which is an order of magnitude less

The biggest hassle for us has been the weak MySQL support in Python. The
spec keeps changing and the interface is raw. (That should not be read
as a complaint directed at the people who have worked on the current
modules. I am tremendously grateful for their existence; I just wish the
community had more resources to throw at the problem.) We've written a
dictionary-based interface to sit on top of the modules, but it's
remains the source of much wailing and gnashing of teeth.

In article <9N4L4.499$wYl.191816704 at>,
  "Fredrik Lundh" <effbot at> wrote:
> Charley Horse <someone at> wrote:
> > It was just an unexpected surprise. I'm fairly new to all of this
> > always heard of CGI in the context of "you don't have to user CGI
> > anymore because of the fancy new blah blah technology we offer!"
> in Python land, that fancy technology is called
> Zope (
> well worth checking out, but be careful -- your
> brain might explode.
> </F>

Sent via
Before you buy.

More information about the Python-list mailing list