|
Original |
Translation |
|
1117
|
Using a Python shell script to put up a Python interpreter window from inside your Windows app is not a good idea; the resulting window will be independent of your app's windowing system. Rather, you (or the wxPythonWindow class) should create a "native" interpreter window. It is easy to connect that window to the Python interpreter. You can redirect Python's i/o to _any_ object that supports read and write, so all you need is a Python object (defined in your extension module) that contains read() and write() methods.
|
|
|
1118
|
How do I use Python for CGI?
|
|
|
1119
|
On the Microsoft IIS server or on the Win95 MS Personal Web Server you set up Python in the same way that you would set up any other scripting engine.
|
|
|
1120
|
|
|
|
1121
|
|
1122
|
and enter the following line (making any specific changes that your system may need)::
|
|
|
1123
|
.py :REG_SZ: c:\<path to python>\python.exe -u %s %s
|
|
|
1124
|
This line will allow you to call your script with a simple reference like: ``http://yourserver/scripts/yourscript.py`` provided "scripts" is an "executable" directory for your server (which it usually is by default). The :option:`-u` flag specifies unbuffered and binary mode for stdin - needed when working with binary data.
|
|
|
1125
|
In addition, it is recommended that using ".py" may not be a good idea for the file extensions when used in this context (you might want to reserve ``*.py`` for support modules and use ``*.cgi`` or ``*.cgp`` for "main program" scripts).
|
|
|
1126
|
In order to set up Internet Information Services 5 to use Python for CGI processing, please see the following links:
|
|