Arbitrarily standardize on 4-space indentation, convert all tabs#45
Open
zandi wants to merge 1 commit intomeshtastic:masterfrom
Open
Arbitrarily standardize on 4-space indentation, convert all tabs#45zandi wants to merge 1 commit intomeshtastic:masterfrom
zandi wants to merge 1 commit intomeshtastic:masterfrom
Conversation
Previously different python files had either 4-space indentation or tab indentation. Choose 4-space indentation because I like it, but also PEP-8 explicitly recommends 4-space indentation.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Previously different python files had either 4-space indentation or tab indentation. Choose 4-space indentation because I like it, but also PEP-8 explicitly recommends 4-space indentation.
This was bugging me for a while but I don't want to put this off anymore. Annoying change because many lines change, but there's no functional impact. This PR is somewhat lower priority, if other things are merged and conflict I can just rebase this branch.