Reindent /

Filename Size Date modified Message
Reindent.egg-info
tests
36 B
1.7 KB
10.7 KB
28 B
1.3 KB

Reindent python cleanup script

Released to the public domain, by Tim Peters, 03 October 2000.

Usage:

reindent [-d][-r][-v] [ path ... ]

-d (--dryrun)  Dry run.  Analyze, but don't make any changes to, files.
-r (--recurse) Recurse.  Search for all .py files in subdirectories too.
-v (--verbose) Verbose.  Print informative msgs; else no output.
-h (--help)    Help.     Print this usage information and exit.

Change Python (.py) files to use 4-space indents and no hard tab
characters. Also trim excess spaces and tabs from ends of lines,
and remove empty lines at the end of files.  Also ensure the last line
ends with a newline.

If no paths are given on the command line, reindent operates as a filter,
reading a single source file from standard input and writing the
transformed source to standard output.  In this case, the -d, -r and -v
flags are ignored.

You can pass one or more file and/or directory paths.  When a directory
path, all .py files within the directory will be examined, and, if the -r
option is given, likewise recursively for subdirectories.

If output is not to standard output, reindent overwrites files in place,
renaming the originals with a .bak extension.  If it finds nothing to
change, the file is left alone.  If reindent does change a file,
the changed file is a fixed-point for future runs (i.e., running
reindent on the resulting .py file won't change it again).

The hard part of reindenting is figuring out what to do with comment
lines.  So long as the input files get a clean bill of health from
tabnanny.py, reindent should do a good job.