I'm not sure of the best solution for the original question,
but, in case anyone missed the point, the direction I was
headed with some of my previous posts was to look at the
possibility of *post-compiler* optimizing Python byte-code.
The reason for not doing this in the compiler, is that one
may need to turn it on and off by function, rather than my
module or globally. I won't go into details now, but I just
wanted to register this possibility as one more thing to take
into account. I was assuming that the optimized code would
be re-written into the original .pyc file, and I hadn't yet
considered the case where that was not writable.
What exactly is the current behaviour when the .pyc file is
not writable ? Does it not get written, or does it get
written to the current directory ?
- Steve Majewski (804-982-0831) <sdm7g@Virginia.EDU>
- UVA Department of Molecular Physiology and Biological Physics