One additional issue: The system produces pyo and pyc files for all the
.py files it finds. That is good for the files that go into site-packages
because they are intended to be executed from there, but might not be so
good for documentation files such as examples and code-snippets that are
intended to be run or otherwise used in user-space.
The commands:
find . -type f -name *.pyc -exec rm -f {} \;
find . -type f -name *.pyo -exec rm -f {} \;
executed at some point in the process at the root of the default
documentation directory after the .pyc and .pyo files have been created
can remove them. However, I can't seem to figure out where to put the
statements. Also, might there be a way to prevent the byte compiling of
documentation files?
Stan Klein
Show replies by date