Home / Browse / Webware for Python / Mail / Archive

Webware for Python

Email Archive: webware-discuss (read-only)

[Webware-discuss] standalone and cgi

From: Jeff Johnson <jeff@ff...> - 2000-10-05 17:02

I just downloaded the Standalone utility and I get the following error when
trying to build a standalone version (see below).  BTW, I read a description
of what the standalone tool does and it doesn't sound like it would be
faster than calling .py.  It sticks the python15.dll and all the script code
in a compressed attachment to the executable launcher.  The launcher
decompresses everything and then runs the script.  Sounds like a crapload of
overhead if this must be done for each page request.  <disclaimer>I spent a
whole 23 seconds reading about it and maybe I'm completely
wrong..</disclaimer>

Getting back to the real topic, assuming that IIS 5.0 fixed the CGI handler,
we still have the problem that http:\\localhost\webkit.py\ works but without
the trailing slash it doesn't.  Could it be that having .py as the CGI
script extension is confusing webkit?  Maybe it see's a .py in the URL and
tries to open it from the default directory (Examples)?  ... Nope, I changed
it to .py1 and added that mapping, it still didn't work.


C:\bin\pyexe>simple.py WebKit.py
File 'WebKit.cfg' already exists. Overwrite? [yn]y
> "C:\Python20\python.exe" C:\bin\pyexe\Builder.py WebKit.cfg
opts: []
args: ['WebKit.cfg']
Initializing MYSTANDALONE
Analyzing python dependencies of carchive_rt
C:\bin\pyexe\support\carchive_rt.py

Traceback (most recent call last):
  File "C:\bin\pyexe\Builder.py", line 502, in ?
    main(opts, args)
  File "C:\bin\pyexe\Builder.py", line 473, in main
    target = makeTarget(cfg, section)
  File "C:\bin\pyexe\Builder.py", line 416, in makeTarget
    return dispatch[cfg.get(section, 'type')](cfg, section, optcnvrts)
  File "C:\bin\pyexe\Builder.py", line 337, in __init__
    FullExeTarget.__init__(self, cfg, sectnm, cnvrts)
  File "C:\bin\pyexe\Builder.py", line 281, in __init__
    ArchiveTarget.__init__(self, cfg, sectnm, cnvrts)
  File "C:\bin\pyexe\Builder.py", line 248, in __init__
    self._dependencies.merge(carchmodule.dependencies())
  File "C:\bin\pyexe\MEInc\Dist\resource.py", line 138, in dependencies
    return self.modules + self.binaries
  File "C:\bin\pyexe\MEInc\Dist\resource.py", line 118, in __getattr__
    for (nm, path) in archivebuilder.Dependencies(self.path):
  File "C:\bin\pyexe\MEInc\Dist\archivebuilder.py", line 79, in Dependencies
    rslt.append(k, v.__file__)
TypeError: append requires exactly 1 argument; 2 given

Thread View

Thread	Author	Date
[Webware-discuss] standalone and cgi	Jeff Johnson <jeff@ff...>

Re: [Webware-discuss] standalone and cgi

From: Chuck Esterbrook <echuck@mi...> - 2000-10-05 17:17

At 01:01 PM 10/5/00 -0400, Jeff Johnson wrote:
>TypeError: append requires exactly 1 argument; 2 given

That, my friend, looks like a Python 2.0 error. append(a, b) must now be 
written as extend([a, b]) or append(a); append(b).

Regarding the trailing slash, I still suspect environment variables. I 
remember Apache either put a slash or did not put a slash, in one kind of 
circumstance, on the URL path contrary to what was really passed in and I 
remember coding for this.

Can you cook up a little servlet to print os.environ() in a readable 
format? I think there's even an HTMLForDict in WebUtils.WebFuncs.

-Chuck

Re: [Webware-discuss] standalone and cgi

From: Geoff Talvola <gtalvola@na...> - 2000-10-05 18:15

Jeff Johnson wrote:

> I just downloaded the Standalone utility and I get the following error when
> trying to build a standalone version (see below).  BTW, I read a description
> of what the standalone tool does and it doesn't sound like it would be
> faster than calling .py.  It sticks the python15.dll and all the script code
> in a compressed attachment to the executable launcher.  The launcher
> decompresses everything and then runs the script.  Sounds like a crapload of
> overhead if this must be done for each page request.  <disclaimer>I spent a
> whole 23 seconds reading about it and maybe I'm completely
> wrong..</disclaimer>

Here's a quote from the Installer documentation (about the Simple tool, but the
Standalone tool uses the same method):

"This configuration is the best balance between speed and minimal dependencies.
Generally, all resources will be in one directory (or tree, if something like Tk
is included) on the user's harddisk, making de-install very simple indeed. The
installed app will be fast - faster than stock Python, which has to hunt all
over your harddisk on each import."

So the Standalone tool does produce a fast executable.  You're probably
confusing it with the Freeze tool which is also part of the Installer package --
that also packs dlls into the same file, then has to unpack them every time the
program runs, which makes for a very slow executable.  In any case, I did
actually time it and the executable produced by Standalone was faster than
running it via python.exe.

Anyhow, from looking at your error it looks like Installer hasn't been ported to
Python 2.0.  You'll have to ask Gordon McMillan about that, or try using Python
1.5.2.

--

- Geoff Talvola
  Parlance Corporation
  gtalvola@...

Re: [Webware-discuss] standalone and cgi

From: Dave <dwallace@de...> - 2000-10-05 23:13

Chuck Esterbrook wrote:

> 
> That, my friend, looks like a Python 2.0 error. append(a, b) must now 
> be  written as extend([a, b]) or append(a); append(b).
> 
Actually,  error.append((a,b)) is equivalent.


Dave.