Re: revised import.c
Gerry Stringer (email@example.com)
Sat, 31 Jul 93 13:23:31 BST
>I can see why you'd want this in certain cases, but when I designed
>this code I made a conscious decision to require that the .py should
>file be there for the .pyc file to be valid -- unlike Emacs .elc
>files, .pyc files can be considered as pure caches and are managed
>completely automatic. Perhaps Lance's version can be made into a
>compile-time or run-time option?
My vote goes for some runtime control in fact, as I've mentioned
before, I'd actually like to be able to 'compile' Python code and run
Just a thought.