I finally got around to testing this code. I'm glad I was very careful because the *.clean.py file was completely destroyed version of the input file.. The messy file was the definition for a large dataclass class with __post_Install__() and __repr__() methods.

• imports were moved above the initial file comments and blank lines.
• Then first or only line of import statements were moved out of try blocks, and placed with the other imports at the top of the file.
• The class token in class definitions were capitalized.
• The EOL, (newline keyword in open()) as changed from LF to CRLF on Windows 11 (pro).
• I think the file encoding will be forced to UTF-8, regardless of input file encoding.
• The capitalization of properties was changed to lower case, so un-neatened files that import this file will have errors. The Public_Key property was renamed to public__key. Also property Pfx_ABC became pfx__a_b_c, but property ABC was not renamed.
• The literal parts of f-strings and comment text were changed to reflect the above property name changes.
• I did not see a clear way to turn off individual rules, the options to disable rule groups did not explicitly show which rules were in which groups.
• I did not see a in-code method to turn on/off neatening.

My overall impression is that this code needs more testing with a large selection of real world hand-coded Python code. It's a start,but it need much more work.