Added VS Code to coding conventions. Replaced PyCharm references to IDE where needed.

Author: anenadic

episodes/15-coding-conventions.md

@@ -111,29 +111,45 @@ Whichever you choose, be consistent throughout the project.
 
 ::::::::::::::::::::::::::::::::::::::::::::::::::
 
-PyCharm has built-in support for converting tab indentation to spaces
-"under the hood" for Python code in order to conform to PEP 8.
-So, you can type a tab character and PyCharm will automatically convert it to 4 spaces.
-You can control the amount of spaces that PyCharm uses to replace one tab character
-or you can decide to keep the tab character altogether and prevent automatic conversion.
+IDEs typically let you control text indentation and whether you would like to use spaces or tab stops.
+Such IDEs have built-in support for converting tab indentation to spaces "under the hood" for Python code in order to conform to PEP 8.
+So, you can type a tab character and your IDE will automatically convert it to 4 spaces.
+You can also control the amount of spaces that the IDE uses to replace one tab character or you can decide to keep the tab character altogether and prevent automatic conversion.
+
+::: group-tab
+
+### PyCharm
+
+By default, PyCharm inserts spaces and uses 4 spaces per tab key.
 You can modify these settings in PyCharm's `Settings`\>`Editor`\>`Code Style`\>`Python`.
 
-![](fig/pycharm-indentation.png){alt='Python code indentation settings in PyCharm' .image-with-shadow width="800px"}
+![](fig/pycharm-indentation.png){alt='Python code indentation settings in PyCharm' .image-with-shadow width="1000px"}
 
 You can also tell the editor to show non-printable characters
 if you are ever unsure what character exactly is being used
 by selecting `Settings` > `Editor` > `General` > `Appearance` then checking "Show whitespaces" option.
 
 ![](fig/pycharm-whitespace.png){alt='Python code whitespace settings in PyCharm' .image-with-shadow width="800px"}
 
-There are more complex rules on indenting single units of code that continue over several lines,
-e.g. function, list or dictionary definitions can all take more than one line.
-The preferred way of wrapping such long lines is
-by using Python's implied line continuation inside delimiters such as
-parentheses (`()`),
-brackets (`[]`)
-and braces (`{}`),
-or a hanging indent.
+### VS Code
+
+By default, VS Code inserts spaces and uses 4 spaces per tab key. 
+You can modify these settings in VS Code's user or workspace settings (`File -> Settings` then search for `tabSize` and enter the value you want).
+You also need to make sure `Editor: Detect Indentation` field is checked.
+
+![](fig/vscode-whitespace.png){alt='Python code whitespace settings in VC Code' .image-with-shadow width="1000px"}
+
+If you are editing `settings.json` file manually - these are the 2 properties you need to set:
+
+```yaml
+  "editor.insertSpaces": true,
+  "editor.tabSize": 4,
+```
+
+:::
+
+There are more complex rules on indenting single units of code that continue over several lines, e.g. function, list or dictionary definitions can all take more than one line.
+The preferred way of wrapping such long lines is by using Python's implied line continuation inside delimiters such as parentheses (`()`), brackets (`[]`) and braces (`{}`), or a hanging indent.
 
 ```python
 # Add an extra level of indentation (extra 4 spaces) to distinguish arguments from the rest of the code that follows
@@ -168,8 +184,7 @@ a_long_list2 = [
 ]
 ```
 
-More details on good and bad practices for continuation lines can be found in
-[PEP 8 guideline on indentation](https://www.python.org/dev/peps/pep-0008/#indentation).
+More details on good and bad practices for continuation lines can be found in [PEP 8 guideline on indentation](https://www.python.org/dev/peps/pep-0008/#indentation).
 
 ### Maximum Line Length
 
@@ -462,8 +477,7 @@ Fix the discovered inconsistencies and commit them to the feature branch.
 
 ## Solution
 
-Modify `inflammation-analysis.py` from PyCharm,
-which is helpfully marking inconsistencies with coding guidelines by underlying them.
+Modify `inflammation-analysis.py` from your IDE, which is helpfully marking inconsistencies with coding guidelines by underlying them.
 There are a few things to fix in `inflammation-analysis.py`, for example:
 
 1. Line 30 in `inflammation-analysis.py` is too long and not very readable.
@@ -657,13 +671,10 @@ Functions:
 ...
 ```
 
-The docstring for a function or a module
-is returned when calling the `help` function and passing its name -
-for example from the interactive Python console/terminal available from the command line
-or when rendering code documentation online
-(e.g. see [Python documentation](https://docs.python.org/3.11/library/index.html)).
-PyCharm also displays the docstring for a function/module
-in a little help popup window when using tab-completion.
+The docstring for a function or a module is returned when calling the `help` function and passing its name - 
+for example from the interactive Python console/terminal available from the command line or when rendering code documentation online (e.g. see [Python documentation](https://docs.python.org/3.11/library/index.html)).
+
+Your IDE will also display the docstring for a function/module in a little help popup window when using tab-completion or when hovering your mouse over the function/module name.
 
 ```python
 help(fibonacci)

episodes/17-section1-optional-exercises.md

@@ -48,9 +48,8 @@ Some suggestions to try:
 - [Sublime Text](https://www.sublimetext.com/)
 - [RStudio](https://posit.co/download/rstudio-desktop/)
 
-When compared to PyCharm, the IDEs listed above are advanced source code editors capable of functioning as IDEs.
-To function as an IDE, you have to manually install plugins for these tools to obtain more advanced features -
-such as support for a specific programming language or unit testing.
+The IDEs listed above are advanced source code editors capable of functioning as IDEs by manually installing plugins 
+and add-ons for these tools to obtain more advanced features - such as support for a specific programming language or unit testing.
 
 What do you prefer, a lot of tooling out of the box or a lightweight editor with optional extensions?
 

episodes/21-automatically-testing-software.md

@@ -454,19 +454,7 @@ for a particular project or team, so you may want to revisit it at a later date.
 
 If you have already installed `pytest` package in your virtual environment,
 you can skip this step.
-Otherwise, as we have seen, we have a couple of options for installing external libraries:
-
-1. via PyCharm
-  (see ["Adding an External Library"](13-ides.md) section
-  in ["Integrated Software Development Environments"](13-ides.md) episode),
-  or
-2. via the command line
-  (see ["Installing External Libraries in an Environment With `pip`"](12-virtual-environments.md) section
-  in ["Virtual Environments For Software Development"](12-virtual-environments.md) episode).
-
-To do it via the command line -
-exit the Python console first (either with `Ctrl-D` or by typing `exit()`),
-then do:
+Otherwise, make sure you do it - e.g. via the command line terminal:
 
 ```bash
 $ python3 -m pip install pytest

episodes/52-assessing-software-suitability-improvement.md

@@ -51,7 +51,7 @@ and provide feedback.
 1. Decide as a team on one of your repositories that will represent your group.
   You can do this any way you wish,
   but if you are having trouble then a pseudo-random number might help:
-  `python -c "import numpy as np; print(np.random.randint(low=1, high=<size_group_plus_1>))"`
+  `python3 -c "import numpy as np; print(np.random.randint(low=1, high=<size_group_plus_1>))"`
 2. Add the URL of the repository to
   the section of the shared notes labelled 'Decide on your Group's Repository',
   next to your team's name.

episodes/fig/vscode-whitespace.png

@@ -303,10 +303,10 @@ poetry --version  # check we have access to the poetry executable
 - The current way of sharing our package is:
   ```bash
   git clone <our_repo>
-  python -m venv venv
+  python3 -m venv venv
   . venv/bin/activate
   pip install -r requirements.txt --editable .
-  python inflammation-analysis.py
+  python3 inflammation-analysis.py
   ...
   ```
   - and then there are a bunch of hoops to jump through to make sure import statements work when testing