Skip to content
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.

Add isort import style linter #217

merged 7 commits into from Jan 30, 2019

Add isort import style linter #217

merged 7 commits into from Jan 30, 2019


Copy link

@c-w c-w commented Jan 30, 2019

As discussed in #212 (comment), this pull request adds the isort linter to ensure that all the import styles are always consistent.

The linter is configured to follow the PEP-8 import style such as having separate blocks for standard library, third party and own imports, etc. Additionally, the linter is configured to force imports to be one per line to ensure that diffs are clean (e.g. adding or removing an import will be an easily visible full line diff instead of intermingled with other imports).

Editor plugins to automatically run isort are also available.

All Submissions:

  • Have you followed the guidelines in our Contributing document?

  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?

  • Does your PR follow our Code of Conduct?

  • Have you added an explanation of what your changes do and why you'd like us to include them?

  • Does each method or function "do one thing well"? Reviewers may recommend methods be split up for maintainability and testability. Not applicable: linting change

  • Is this code designed to be testable? Not applicable: linting change

  • Is the code documented well? Not applicable: linting change

  • Does your submission pass existing tests (or update existing tests with documentation regarding the change)?

  • Have you added tests to cover your changes? Not applicable: linting change

  • Have you linted your code prior to submission?

  • Have you updated the documentation and README? Not applicable: linting change

  • Is PII treated correctly? In particular, make sure the code is not logging objects or strings that might contain PII (e.g. request headers). Not applicable: linting change

  • Have secrets been stripped before committing? Not applicable: linting change

@c-w c-w mentioned this pull request Jan 30, 2019
13 tasks
@c-w c-w force-pushed the isort branch 3 times, most recently from 9192306 to e6a6425 Compare January 30, 2019 17:14
For some reason this doesn't work if the option is set in setup.cfg,
likely because the special characters in the template path confuse the
isort tool.
@sayar sayar merged commit 03cd0e6 into master Jan 30, 2019
@sayar sayar deleted the isort branch January 30, 2019 19:18
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
None yet

Successfully merging this pull request may close these issues.

None yet

2 participants