Skip to content

Commit

Permalink
Readme: remove Flake8 mentions
Browse files Browse the repository at this point in the history
  • Loading branch information
josephsl committed Jun 29, 2024
1 parent 9a73405 commit 04c1036
Showing 1 changed file with 0 additions and 2 deletions.
2 changes: 0 additions & 2 deletions readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,6 @@ This template provides the following features you can use during NVDA add-on dev

In addition, this template includes configuration files for the following tools for use in add-on development and testing (see "additional tools" section for details):

* Flake8 (flake8.ini): a base configuration file for Flake8 linting tool based on NVDA's own Flake8 configuration file.
* Ruff (pyproject.toml/tool.ruff sections): a Python linter written in Rust. Sections starting with tool.ruff house configuration options for Ruff.
* Configuration for VS Code. It requires NVDA's repo at the same level as the add-on folder containing your actual source files, with prepared source code (`scons source`). preparing the source code is a step in the instructions for building NVDA itself, see [The NVDA Repository](https://github.com/nvaccess/nvda) for details.
* Place the .vscode in this repo within the addon folder, where your add-on source files (will) reside. The settings file within this folder assumes the NVDA repository is within the parent folder of this folder. If your addon folder is within the addonTemplate folder, then your NVDA repository folder needs to also be within the addonTemplate folder, or the source will not be found.
Expand Down Expand Up @@ -135,7 +134,6 @@ Note: you must fill out this dictionary if at least one custom braille table is

The template includes configuration files for use with additional tools such as linters. These include:

* Flake8 (flake8.ini): a Python code linter (4.0.1, can be installed with PIP).
* Ruff (pyproject.toml): a Python linter written in Rust (0.4.10 or later, can be installed with PIP).

Read the documentation for the tools you wish to use when building and developing add-ons.
Expand Down

0 comments on commit 04c1036

Please sign in to comment.