[Python-Dev] ISPs and Python

Mark Hammond mhammond@bigpond.net.au
Fri, 16 Jul 1999 09:21:40 +1000


> Remember the days when the big problem was to find an ISP who would
> install Python?  Apparently that problem has gone away...  The problem
> is now to get one that installs a decent set of Python extensions :-)

he he.  Yes, hence I believe the general agreement exists that we should
begin to focus on these more external issues than the language itself.
Pity we all agree, but are still such hackers :-)

> looked at the cgi modules from the book yet to see if they
> give me any added
> benefit. The big problem I came across was my web host, and
> all of the other

From the ISP's POV, this is reasonable.  I wouldnt be surprised to find
they started with the same policy for Perl.  The issue is less likely to be
anything to do with Python, but to do with stability.  If every client was
allowed to install their own extension, then that could wreak havoc.  Some
ISPs will allow a private Python build, but some only allow you to use
their shared version, which they obviously want kept pretty stable.

The answer would seem to be to embrace MALs efforts.  Not only should we be
looking at pre-compiled (as I believe his effort is) but also towards
"batteries included, plus spare batteries, wall charger, car charger and
solar panels".  ISP targetted installations with _many_ extensions
installed could be very useful - who cares if it is 20MB - if they dont
want that, let then do it manually with the standard installation like
everyone else.

There could almost be commercial scope here for a support company.
Offering ISP/Corporate specific CDs and support.  Installations targetted
at machines shared among a huge number of users, with almost every common
Python extension any of these users would need.  Corporates and ISPs may
pay far more handsomly than individuals for this kind of stuff.

I know I am ranting still, but I repeat my starting point that addressing
issues like this are IMO the single best thing we could do for Python.  We
could leave the language along for 2 years, and come back to it when this
shite is better under control :-)

of-course-you-should-all-do-that-while-I-continue-to-hack<wink>-ly,

Mark.