Today I had the problem described (and solved) here:

Hi all,
Some of you may have struck an "Internal Error 500" error when
trying to
use Python as an Active Scripting language inside IIS using the latest
ActivePython builds.

The solution to this appears to be the following:
* Change to the "Python21\win32comext\axscript\client" directory.

* Execute "python pyscript.py --unregister"

* Execute "python pyscript.py"

This should make everything work. The key step is the "--unregister"
step -
this clears out some problems in the registry. Just doing the last
registation step does not solve the problem for IIS (even though it
solve the problem for IE and other scripting environments).

We will have this fixed in the next ActivePython release.



This was posted in 2001. Was this fixed and broken again?

FWIW, I had this problem on Win2k Server, but did not have the same
issue on Win2k Pro. Both platforms are using Python 2.3.2. It may simply
be due to the order in which I installed Python, set up the webserver,
installed win32all, or upgraded Python on each system.

Robert Brewer
Amor Ministries
fumanchu at amor.org

From http Mon Dec 8 20:56:10 2003
From: http (Paul Rubin)
Date: 08 Dec 2003 11:56:10 -0800
Subject: from spam import eggs, spam at runtime, how?
References: <br99tv8mgguso67p2a8h8p8sctr2o7olse@4ax.com>
Message-ID: <7xhe0bf5id.fsf@ruckus.brouhaha.com>

Rene Pijlman <reply.in.the.newsgroup at my.address.is.invalid> writes:
spam = __import__('spam.eggs')
eggs = spam.eggs
Yes, and a bit more elegant (pythonic?). Thanks.
Another way:

exec 'import spam'

Search Discussions

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppython-list @
postedDec 8, '03 at 7:53p
activeDec 8, '03 at 7:53p

1 user in discussion

Robert Brewer: 1 post



site design / logo © 2022 Grokbase