Sort imports according to PEP8 for gpslogger #29717
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
I have sorted the imports for the
gpslogger
component according to PEP8 using isort.I think it would be good if in the future we can add
isort
to the.pre-commit-config.yaml
.To do that I will first fix all sorting issues per component.
Black and isort do not play nice by default, however, using the following
.isort.cfg
config:it works.
This PR affects:
homeassistant/components/gpslogger/__init__.py
homeassistant/components/gpslogger/config_flow.py
homeassistant/components/gpslogger/device_tracker.py
Checklist:
tox
. Your PR cannot be merged unless tests passIf user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
python3 -m script.hassfest
.requirements_all.txt
by runningpython3 -m script.gen_requirements_all
..coveragerc
.If the code does not interact with devices: