mod_python

[Tetsuo]

´ÐÜøÐÝ ³. <ßÕÝÓãØÝØáâÐ@ÜÐØÛ.ÝÕâ.=?iso-8859-5?Q?=DC=DA?=> wrote in
news:3de714c6$1 at news.mt.net.mk: 

> 
>> I figured out how to get mod_python to work, at last, but I ran into
>> a problem that seems to be fairly common (the solution is harder to
>> find, though). Any code inserted into mptest.py works great. But when
>> I make another file in the same directory, the last thing that was in
>> mptest goes into that file, even if mptest doesn't exist any more.
>> Must be browser cache or something... Well, I have no idea, since
>> it's a different file. Does Apache have a cache, too? I have heard
>> that some mistake in the configuration can make Apache keep referring
>> to mptest. But I can't find how to fix it...
> 
> Thats the way mod_python works. read the documentation :)
> 
> You have registered mptest.py to be a handler for all requests 
> ending in ".py".
> 
> 
> 

Here's what I can gather: if I want to have another script, I have to put 
it in a new directory and create a directive in the conf for that new 
file.

That sounds so complex, clumsy and dumb that it's probably not the way. 
How do I make every script handle itself? I tried the publisher handler, 
and it proved useless.

I thought about importing everything to one script from others, but that 
isn't what I need at all. That's just pointless.

And how do I make it so typing in a directory gives me a page (index.htm) 
instead of a list of the files in the directory? (Goes to take another 
look at the publisher)