how python works

[Mahmood Naderan]

>Neither/both, depending on your definition of either word. It does not
>compile to machine code: it compiles to byte code (which it then
>usually, but not always, stores in a pyc file alongside the py file). It
>does not interpret the Python code on the fly, it is a VM which
>"interprets" the byte code.


>So, it's an interpreter that compiles the code first.

Thanks. I got it.
 
// Naderan *Mahmood;




________________________________
From: Stephen Hansen <me+list/python at ixokai.io>
To: python-list at python.org
Sent: Fri, July 30, 2010 11:13:27 PM
Subject: Re: how python works

On 7/30/10 11:16 AM, Mahmood Naderan wrote:
> So is it a compiler or interpreter?

Neither/both, depending on your definition of either word. It does not
compile to machine code: it compiles to byte code (which it then
usually, but not always, stores in a pyc file alongside the py file). It
does not interpret the Python code on the fly, it is a VM which
"interprets" the byte code.

--

  Stephen Hansen
  ... Also: Ixokai
  ... Mail: me+list/python (AT) ixokai (DOT) io
  ... Blog: http://meh.ixokai.io/


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-list/attachments/20100730/a4597c8e/attachment.html>