[Pythonmac-SIG] MacPython, CGI and free cd's
Just van Rossum
Thu, 3 Aug 2000 16:18:52 +0100
At 4:00 PM +0200 03-08-2000, Jack Jansen wrote:
>> Unfortunately for every change you will have to create the applet again.
>Okay, this I'd like to change.
Which is easy if we make the LONG_RUNNING switch accesible from a menu. It
could store the last value in a prefs file, and the default setting could
>This behaviour is nice once you have the cgi
>script working, but for debugging it's much easier if the PythonCGISlave
>engine would simply execfile() the script in a fixed folder.
I don't quite understand the fixed folder idea: why not put it where the
web server wants it? (I mean, I do understand the idea in the context of
your proposal, but in the context of PythonCGISlave as it is.)
>> I don't see why we should create different default behavior than for unix.
>Okay, let's try a different angle: do you _oppose_ this behaviour or is it
>just that you don't think it worth it? (i.e. would you mind if I implemented
I think it's simply not worth it...
>> And make the UI even messier than it already is? ;-)
>Ok. We can always put some extensions in the IDE extension folder to give
>access to this.
>I'm getting so enthusiastic about the project by now that I may well try and
>find some time to do the last little bits myself, as 99% of the code is
>already there (and I'd probably have to do the organization myself anyway, as
>that's mostly a question of beating on the installer).
>What do you think, is CGI scripting important enough to put PythonCGISlave in
>the toplevel folder, along with a CGI folder?
>Also, would you be opposed to renaming it to CGIPython.cgi?
No; except when used as a slave (though a *.py action handler) it doesn't
need to end in .cgi.
Please also have a look at BuildCGIApplet; it uses PythonCGISlave.py;
there's a simple switch in the latter to distinguish between the two