Tomer

@MeitarR

# New smell ### Smelly code ```py fp = open(path,args,kwargs) # Body fp.close ``` ### Fixed code ```py with open(path,args,kwargs as fp: # Body ``` ### Why is it smelly?...

This should probably happen after #21

Receive a path to the formatter executable and run it after fixing any smells

Allow users to run the fixer with a pre-commit hook

Ideally automatically from pull requests and git tags

Use f-string instead of string.format

1

# New smell ### Smelly code ```py "a={},b={}".format(a,b) ``` ### Fixed code ```py f"a={a},b={b}" ``` Potential gotchas: - [ ] warn only on py3.6+ - [ ] if the expression...

This will probably be done by caching code before changes in a dot folder before overwriting a file, and restoring it from the cache later

Nothing too fancy, something on github.io. A nice side project when the project is more well-formed

An extension of #4 The function `range(start,stop,step)` can be replaced with `enumerate(islice(iterable,start,stop,step))` or even just `islice` if the index isn't used out of the assign. for example ```py for i...