Location of bytecode files (pyc)

Peter Hansen peter at engcorp.com
Wed Sep 3 21:24:14 CEST 2003


Rim wrote:
> 
> > If you're on Windows say:
> >
> > del /S *.pyc
> >
> > to remove all .pyc's from cwd and below.
> 
> Yes, and in linux 'find . -name "*.pyc" -exec rm -rf {} \;', but that
> is not the point. I did not ask about how to remove pyc files, I asked
> about placing them far from source code, in another directory, so they
> would not be seen by the backup software.
> 
> The backup software runs continuously day, night, weekends, all the
> time. Sweeping the pyc's under the carpet each time the backup is
> about to be saving my files is impossible. That is why we store all
> gcc object files and executables we produce on non-backed up
> filesystems by prefixing target filenames in makefiles with a variable
> like $OBJECT_DIR and $EXEC_DIR.

You have a fancy backup system like this, involving hundreds of Gigs,
and it can't apply a simple filter to avoid .pyc and .obj files?!

-Peter




More information about the Python-list mailing list