Complete.Org: Mailing Lists: Archives: gopher: April 2002:
[gopher] Re: Pygopherd nearing gopherd replacement
Home

[gopher] Re: Pygopherd nearing gopherd replacement

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: Pygopherd nearing gopherd replacement
From: John Goerzen <jgoerzen@xxxxxxxxxxxx>
Date: Fri, 5 Apr 2002 09:40:18 -0500
Reply-to: gopher@xxxxxxxxxxxx

On Thursday, April 4, 2002, at 10:47  PM, Timm Murray wrote:

> Python saves the compiled output of the script after the first run, so 
> new =
> runs of the=20
> script should run at near native speeds anyway.

Well, yes and no.  Python does not save native machine code, it saves 
Python bytecode -- similar in concept to Java bytecode.  This still gets 
interpreted -- it just saves the parsing step, which generally only 
reduces program load time.

This can be a win if you're on a really slow machine or if you're 
invoking it a LOT (ie, a CGI), but otherwise the difference is generally 
unnoticeable.

-- John



[Prev in Thread] Current Thread [Next in Thread]