stlib name clash when using python as ASP language

[Gabriel Genellina]

En Sun, 04 Feb 2007 09:53:22 -0300, Joost <JoostMoesker at gmail.com>  
escribió:

>> You *assume* that [0] is the IIS path, but perhaps some other imported
>> module changed sys.path too, and now it's not the first one anymore.
>> If you know exactly the path, try sys.path.remove(iis_path).
>>
>
> It's was a hack and definitely not meant to go in to production ;)
> Since gzip.py lives in python24\lib I thought setting sys.path[0] to
> python24\lib would load this load this module, no matter what.
> However, in some magically way the sys.path gets modified during the
> request by IIS. Maybe IIS resets the global sys.path per new request,
> causing sporadic problems when request are handled concurrently? I
> just don't know. The iis/inetsrv path is included in sys.path for a
> reason and I don't want to fiddle around with sys.path to create
> problems in other parts of the code. I was wandering if there is some
> way to prevent a  name clashes by using a custom importer or something
> like that.

Python 2.5 has absolute and relative imports, that should handle such  
problems in the future.
But in your case I can think of:
- *prepend* python24\lib instead of replacing index 0: sys.path.insert(0,  
python24\lib)
- copy gzip.py to another, empty directory, and put *that* directory in  
front of sys.path
- play with ihooks.py

-- 
Gabriel Genellina