RetroSearch Browse

Tue May 11 10:59:13 EDT 2004 · https://mail.python.org/pipermail/python-dev/2004-May/044753.html

On May 11, 2004, at 1:04 AM, Greg Ewing wrote:

> Bob Ippolito <bob at redivi.com>:
>
>> Doing extensive checking of bytecode at runtime would make Python's
>> interpreter much slower than it already is.
>
> Another approach would be to make the bytecode a special object
> that can only be created by the compiler (or other C code). If
> you wanted custom bytecode, you'd have to build an AST and feed
> it to the compiler, or write an extension module.
>
> No doubt some bytecode hackers would find this too limiting,
> however.

Then you should give up .pyc files, because I'd imagine they have the 
problems as ceval does if someone decided to change some stuff by hand.

-bob

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2004-May/044753.html below:

[Python-Dev] Is core dump always a bug? Advice requested