Finding Python hosting is difficult and all are expensive. I find that a dis-incentive to try it. Even if we leave that factor out, I find the plethora of options out there confusing. I plan to try Nevow sometime in the future.
Persistent processes for servers (eg: twisted) will not be as successfull as PHP. CGI or mod_python are the only affordable way to go with Python. Nevow works partially with WSGI (WSGI knows nothing about LivePage and Guard). If you are looking for XMLHttpRequest support, try wallaby.
Deru.net is very affordable and reliable, and Python runs great there.
Now this is interesting. I am running hosting besides other things and I'd love to provide Python too. Is there a consensus what that means actually? Is it CGIs in Python, Zope, Webware, Twisted, or mod_python within Apache? Or all of them? Or anything else? Then, there is a question how to set them up when you have decided - what access rights, permissions, etc.
I have a couple of my own projects there and they use mod_python. This includes some hacking in the mod_rewrite, or mod_alias for every project that needs python for it to work. PHP is different: you just drop the files in the directory and it just works.
Maybe when ordinary administrators (= not using Python every day) know how to set it up, there will be plenty of Python hostings; when it is as easy as issuing apt-get install php4...
jbar# Jiri Barton
This is EXACTLY why Python is losing out to PHP.
There are WAY too many options (Zope, Twisted, CherryPy, Paste, Django, Quixote, ad nausem...) and ALL of them require a long running process (no-no in most hosting scenarios) - which leaves people with CGI, which has been widely accepted as NOT the right way to build large web apps.
This means until we have totally clean Python integration with apache (mod_python is too low level for most people, we don't want to care about returning http response codes - Python is high level remember!), or tomcat for Python <- this is what I think we need most btw (and Zope is an abomination in my eyes and nowhere close to filling this need), we're suck using Python as a client side language.# anonymous
If we have enough clear documentation for mod_python then I think it can be a killer web language. I have to read mod python tutorial 5 times to get the information that Mr.Grish states. IMO , it's a splendid tool and I am beginning to write applications in it. It all grinds down to attracting the end users with simple documentation even if it's so low level, the rest follows.