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: Thomas Long <tlong2us@xxxxxxxxx>
Date: Fri, 5 Apr 2002 09:32:21 -0800 (PST)
Reply-to: gopher@xxxxxxxxxxxx

 
  John Goerzen <jgoerzen@xxxxxxxxxxxx> wrote: PLEASE REMOVE ME FROM THIS GROUP. 
NOT SURE HOW I GOT ON BUT OVER MY HEAD. EVEN FOR LURKING! LOL
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




---------------------------------
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax



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