Getting a module's byte code, how?

[Irmen de Jong]

Steve Holden wrote:

> I'm not sure why you think the module's code would be needed once it's 
> been executed. That assigns all necessary code blocks to the functions 
> defined therein, so the code, once the import has been executed, is 
> garbage (from the interpreter's rather process-centric view of things).

Ah, ofcourse. Thanks for this insight.
I may have to rethink some of this...

> I am presuming that this feature of Pyro won't allow a 2.3 system to 
> talk to a 2.4 one, since the byte codes are incompatible.

Correct. However, when you're not using mobile code (the default),
you're fine.

--Irmen