Width of output lines in characters.
String used to indent lines.
This is how the assignment operator is to appear.
... but this is how function-parameter assignment should appear.
This is how function parameters are separated.
... and this is how list items are separated.
... and this is how subscripts are separated.
This separates dictionary keys from values.
... but this separates the start:end indices of slices.
This is the sentinel that marks the beginning of a commentary string.
Hashbang, a line-one comment naming the Python interpreter to Unix shells.
The output character encoding (codec).
Source file encoding.
The %s in the value (if any) is replaced by the value of CODING.
Standard code block (if any).
This is inserted after the module doc string on output.
This is how a blank line is to appear (up to the newline character).
If true, preserve one blank where blank(s) are encountered.
If true, set off comment blocks with blanks.
Split lines containing longer function definitions.
Split lines containing longer function calls.
Split lines containing longer lists or tuples.
Split lines containing longer dictionary definitions.
Split string literals containing more newline characters.
This is how the left margin is to appear.
If true, left justify doc strings.
If true, wrap doc strings to COL_LIMIT.
If true, use quotes instead of apostrophes for string literals.
If true, use apostrophes instead of quotes for string literals.
If true, try to decode strings.
Attempt to use the character encoding specified in the input (if any).
This is how the newline sequence should appear.
Normally, the first thing that looks like a newline
sequence on input is captured and used at the end of every
line of output. If this is not satisfactory, the desired
output newline sequence may be specified here.
If true, longer strings are split at the COL_LIMIT.
This literal replaces tab characters in doc strings and comments.
Optionally preserve unassigned constants so that code to be tidied
may contain blocks of commented-out lines that have been no-op'ed
with leading and trailing triple quotes. Python scripts may declare
constants without assigning them to a variables, but PythonTidy
considers this wasteful and normally elides them.
Optionally omit parentheses around tuples, which are superfluous
after all. Normal PythonTidy behavior will be still to include them
as a sort of tuple display analogous to list displays, dict
displays, and yet-to-come set displays.
When PythonTidy splits longer lines because MAX_SEPS
are exceeded, the statement normally is closed before the margin is
restored. The closing bracket, brace, or parenthesis is placed at the
current indent level. This looks ugly to "C" programmers. When
JAVA_STYLE_LIST_DEDENT is True, the closing bracket, brace, or
parenthesis is brought back left to the indent level of the enclosing
statement.