Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Muttley@DastardlyHQ.org Newsgroups: comp.lang.c Subject: Re: Python recompile Date: Fri, 7 Mar 2025 09:56:09 -0000 (UTC) Organization: A noiseless patient Spider Lines: 15 Message-ID: References: <20250304092827.708@kylheku.com> Injection-Date: Fri, 07 Mar 2025 10:56:09 +0100 (CET) Injection-Info: dont-email.me; posting-host="f107a31ee72b30696d1d83f0cc00b567"; logging-data="3660312"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1893Y5QSn8+2ZV9rI7rD8DS" Cancel-Lock: sha1:Ue46ESVD1cuRG7L0KF9D/yD51cA= Bytes: 2139 On Thu, 6 Mar 2025 21:22:19 -0000 (UTC) Lawrence D'Oliveiro wibbled: >On Thu, 6 Mar 2025 08:42:03 -0000 (UTC), Muttley wrote: > >> Compilation and runtime are the same thing in Python arn't they? > >No, the code is actually compiled to bytecode, like Java and Perl do, and >UCSD Pascal did before all of them. If that bytecode never sees a file (though apparently it can be written to a pyc file), how is it any different to a normal interpreter simply creating a parse tree or other internal representation of a program that it then runs instead of running the text direct?