[Python-Dev] Splitting up the PVM

Tim Peters tim_one at email.msn.com
Thu Jun 10 07:44:50 CEST 1999

[Guido van Rossum]
> ...
> Here's what I think we should do first (I've mentioned this before but
> nobody cheered me on :-).  I'd like to see this as the basis for 1.6.
> We should structurally split the Python Virtual Machine and related
> code up into different parts -- both at the source code level and at
> the runtime level.  The core PVM becomes a replaceable component, and
> so do a few other parts like the parser, the bytecode compiler, the
> import code, and the interactive read-eval-print loop.  Most object
> implementations are shared between all -- or at least the interfaces
> are interchangeable.  Clearly, a few object types are specific to one
> or another PVM (e.g. frames).  The collection of builtins is also a
> separate component (though some builtins may again be specific to a
> PVM -- details, details!).
> The goal of course, is to create a market for 3rd party components
> here, e.g. Chris' flat PVM, or Skip's bytecode optimizer, or Greg's
> importer, and so on.
> Thoughts?

The idea of major subsystems getting reworked to conform to well-defined and
well-controlled interfaces is certainly appealing.

I'm just more comfortable squeezing another 1.7% out of list.sort() <0.9

trying-to-reduce-my-ambitions-to-match-my-time-ly y'rs  - tim

More information about the Python-Dev mailing list