PEP 304 - Controlling generation of bytecode files

[Oren Tirosh]

On Wed, Jan 29, 2003 at 12:50:57PM -0600, Skip Montanaro wrote:
> 
>     Terry> 3. This proposal changes behavior globally but does not address
>     Terry>    the issue of doing so on a per file basis.
> 
> That's not the intent of this PEP.  It's hard for me to think of a use case
> for module-by-module control over where to write .pyc files.  Can you
> suggest one?

I don't know about module-by-module but would sure be useful on an
importer-by-importer basis when this is combined with the import hooks 
PEP. I guess this PEP needs to pay no special attention to this case
except perhaps mentioning the obvious fact that bytecodepath only affects 
the standard importer.

	Oren