How to use *.py modules instead of *.pyc?

[dsblizzard]

How to use *.py modules instead of *.pyc or automatically recompile
all modules each time I change *.py files?
Thank you in advance.

 

[Chris Rebert]

How to use *.py modules instead of *.pyc or automatically recompile
all modules each time I change *.py files?

IIRC, you shouldn't need to worry about this. Python checks the
modification times on the .py and .pyc files and if the .pyc is older,
it regenerates the .pyc from the .py; thus ensuring that the latest
version of the source file is always used.
What led you to conclude otherwise?

Cheers,
Chris

 

[John Machin]

How to use *.py modules instead of *.pyc or automatically recompile
all modules each time I change *.py files?

You don't need to do anything special. If, when you import foo,
foo.pyc is outdated by changes to the foo.py that is in the same
directory, then foo.py will be compiled to a new foo.pyc -- otherwise
compilation is unnecessary and the existing foo.pyc will be used.

If you think you have a problem, it could be caused by foo.pyc being
in a directory that is in sys.path but you are editing a foo.py that
is not in sys.path.

HTH,
John

 

[Chris Rebert]

How to use *.py modules instead of *.pyc or automatically recompile
all modules each time I change *.py files?
Thank you in advance.

Also, just for the sake of completeness (since John and I have shown
that your real problem lies elsewhere), I happened to come across the
`compileall` module via a Planet Python blog, which mass-compiles
..py-s into .pyc-s:

http://blog.doughellmann.com/2009/01/pymotw-compileall.html

Cheers,
Chris