Skip to content

Commit 9c37320

Browse files
committed
style -> styling
1 parent 324941e commit 9c37320

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

Python/Module5_OddsAndEnds/Writing_Good_Code.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -335,7 +335,7 @@ To conclude, consider that simply knowing that there exists a Python style guide
335335

336336
**Automating Style:**
337337

338-
Although adhering to a clear and consistent style is critical for writing "good code", enforcing such standards can be tedious and labor-intensive. This is especially-true when you begin collaborating with others and working on large projects. Fortunately, there exist several powerful tools that can help automate good code style.
338+
Although adhering to a clear and consistent style is critical for writing "good code", enforcing such standards can be tedious and labor-intensive. This is especially-true when you begin collaborating with others and working on large projects. Fortunately, there exist several powerful tools that can help us automate good code styling.
339339

340340
- [flake8](https://github.com/PyCQA/flake8): Analyzes your code to enforce the PEP8 standards and to catch bad code patterns, such as unused variables.
341341
- IDEs like Visual Studio code and Pycharm will automatically configure themselves to run flake8 or comparable [linters](https://en.wikipedia.org/wiki/Lint_(software)) on your code. They will add visual marks to your code to highlight problematic sections of code. This tool can also be run from the command line, or be configured to run automatically with other IDEs and text editors.

0 commit comments

Comments
 (0)