Python 2.2 + Win32All 146 = Python/ASP Failures
Joe Salmeri
fine until I upgraded from Python 2.1.1 to Python 2.2. Through
experimentation I have basically eliminated all of my ASP code and can still
reproduce the problem.
I have narrowed the problem down to the following sample ASP file:
*** Begin BROKE.ASP ***
<%@language="Python"%>
<html>
<head>
<title>ASP Testing</title>
</head>
<body>
Text goes here
</body>
</html>
*** End BROKE.ASP ***
My configuration is as follows:
Windows XP Professional (all current patches applied)
IIS 5.0 (comes with XP Professional)
Python 2.2
Win32 All Build 146
When the BROKE.ASP file is requested from the web server the first time it
works as expected. If you hit refresh or try to request the page in another
Internet Explorer window you get a blank page back.
Now here's the strange part. If you open up BROKE.ASP in an editor and save
it again (updating the timestamp of the file),
you can now refresh the page in ONE of your IE windows and it will again
work properly. If you try it in a second IE window that one will fail.
Basically it works one time and then fails until the file is updated.
If you modify the above file and change it from
<%@language="Python"%> to <%@language="JavaScript"%>
the problem does not occur, so it definitely appears to be related to
Python/ASP engine.
Anybody seen this or have any idea what is going on?????
Mark Hammond
This ia a bug I am hoping to fix very soon. If you are really keen,
then you can grab the framework.py from win32all-142.exe - you can open
that .exe using WinZip.
Mark.
Joe Salmeri
Things were working fine with 2.1.1 and Win32all build 145.
Do I have to go all the way back to framework.py in build 142 or will the
one in build 145 work?
"Mark Hammond" <mham...@skippinet.com.au> wrote in message
news:3C59DA37...@skippinet.com.au...
Joe Salmeri
I grabbed framework.py from win32all-142.exe and replaced it in the
installation as you suggested. I also deleted the framework.pyc just to
make sure the new version was compiled. Next I restarted the web server,
just as a sanic check to make sure it saw the changes to the python asp
engine.
Repeating my tests with BROKE.ASP (I tested other asp scripts too) and still
had the exact same problem.
Hopefully this may (or may not) give you more insight into the problem.
If I can help out (testing, trying to narrow down the problem further),
please do not hesitate to ask.
"Mark Hammond" <mham...@skippinet.com.au> wrote in message
news:3C59DA37...@skippinet.com.au...
>
Mark Hammond
> Mark,
>
> I grabbed framework.py from win32all-142.exe and replaced it in the
> installation as you suggested. I also deleted the framework.pyc just to
> make sure the new version was compiled. Next I restarted the web server,
> just as a sanic check to make sure it saw the changes to the python asp
> engine.
Sorry - my mistake. You need to go from win32all-140 down to
win32all-133 (inclusive) for a working version :( I have mailed you a copy.
Mark.
Joe Salmeri
So far everything is now working again.
I will report back if I can get any failures.
Thanks again!
"Mark Hammond" <mham...@skippinet.com.au> wrote in message
news:3C5B4A9A...@skippinet.com.au...