Received: with ECARTIS (v1.0.0; list gopher); Fri, 05 Apr 2002 09:40:16 -0500 (EST) Return-Path: Delivered-To: gopher@complete.org Received: from christoph.complete.org (unknown [168.215.193.254]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id AE3E63B80B for ; Fri, 5 Apr 2002 09:40:16 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by christoph.complete.org (Postfix) with ESMTP id 1160C5A422 for ; Fri, 5 Apr 2002 09:40:19 -0500 (EST) Date: Fri, 5 Apr 2002 09:40:18 -0500 Subject: [gopher] Re: Pygopherd nearing gopherd replacement Content-type: text/plain; charset=US-ASCII Mime-Version: 1.0 (Apple Message framework v481) From: John Goerzen To: gopher@complete.org Content-Transfer-Encoding: 8bit In-Reply-To: Message-Id: <0CF95C35-48A3-11D6-857D-0003930BF072@complete.org> X-Mailer: Apple Mail (2.481) X-archive-position: 561 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: jgoerzen@complete.org Precedence: bulk Reply-to: gopher@complete.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-ID: Gopher X-List-ID: Gopher List-subscribe: List-owner: List-post: List-archive: X-list: gopher 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