Message-ID: <20020405173221.14591.qmail@web21110.mail.yahoo.com>
Date: Fri, 5 Apr 2002 09:32:21 -0800 (PST)
From: Thomas Long <tlong2us@yahoo.com>
Subject: [gopher] Re: Pygopherd nearing gopherd replacement
To: gopher@complete.org
In-Reply-To: <0CF95C35-48A3-11D6-857D-0003930BF072@complete.org>
MIME-Version: 1.0
Content-type: text/plain
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


  John Goerzen <jgoerzen@complete.org> 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