Any way to not create .pyc files?

[Peter Hansen]

Lonnie Princehouse wrote:
> We have a site-specific package installed on a network drive[1].  When
> anyone with write access imports this package, the network drive gets
> spammed with .pyc files.
> 
> If these .pyc files exist, they appear to cause problems when other
> users' Python interpreters use them instead of the .py files.  (I know,
> they *should* work, but they don't). 

You didn't really describe the nature of the problem.  Perhaps the whole 
.pyc thing is a bit of a red herring, and the real problem lies 
elsewhere?  What are the actual symptoms of your problem?