diff options
| author |  skullydazed <skullydazed@users.noreply.github.com> | 2020-04-18 13:00:56 -0700 |
|---|---|---|
| committer |  GitHub <noreply@github.com> | 2020-04-18 22:00:56 +0200 |
| commit | 66d94dc22af4fccae2af073c512662ce7eba7d98 (patch) | |
| tree | a720968b0f1951cc2ec920da373701d308f04d88 /docs/coding_conventions_python.md | |
| parent | 5a8f59503e41923030249561e9ef56be62de3efa (diff) | |
| download | qmk_firmware-66d94dc22af4fccae2af073c512662ce7eba7d98.tar.gz | |
Move everything to Python 3.6 (#8835)
Diffstat (limited to 'docs/coding_conventions_python.md')
| -rw-r--r-- | docs/coding_conventions_python.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/coding_conventions_python.md b/docs/coding_conventions_python.md index 1aefc044e..47dff7f8e 100644 --- a/docs/coding_conventions_python.md +++ b/docs/coding_conventions_python.md @@ -2,7 +2,7 @@ Most of our style follows PEP8 with some local modifications to make things less nit-picky. -* We target Python 3.5 for compatability with all supported platforms. +* We target Python 3.6 for compatability with all supported platforms. * We indent using four (4) spaces (soft tabs) * We encourage liberal use of comments * Think of them as a story describing the feature @@ -317,7 +317,7 @@ At the time of this writing our tests are not very comprehensive. Looking at the ## Integration Tests -Integration tests can be found in `lib/python/qmk/tests/test_cli_commands.py`. This is where CLI commands are actually run and their overall behavior is verified. We use [`subprocess`](https://docs.python.org/3.5/library/subprocess.html#module-subprocess) to launch each CLI command and a combination of checking output and returncode to determine if the right thing happened. +Integration tests can be found in `lib/python/qmk/tests/test_cli_commands.py`. This is where CLI commands are actually run and their overall behavior is verified. We use [`subprocess`](https://docs.python.org/3.6/library/subprocess.html#module-subprocess) to launch each CLI command and a combination of checking output and returncode to determine if the right thing happened. ## Unit Tests |