In Python 3.13 venvs created with `python -m venv` include a `.gitignore` by default

[tomneep]

From callout at this end of this section

Note that, since our software project is being tracked by Git, the newly created virtual environment will show up in version control - we will see how to handle it using Git in one of the subsequent episodes.

As the title says, this isn't true in Python>=3.13

[kkh451]

This issue affects the following sections:

• [1.2. Virtual Environments For Software Development - Creating Virtual Environments Using venv] https://carpentries-incubator.github.io/python-intermediate-development/instructor/aio.html#checking-in-changes-to-our-project
• [1.4 - Software Development Using Git and GitHub - Checking-in Changes to Our Project]

Suggested change:

In 1.2

Note that, since our software project is being tracked by Git, the newly created virtual environment may show up in version control. This depends on which version of Python you are working with (<=3.13) - we will see how to handle this using Git in one of the subsequent episodes.

In 1.4

Remember to use meaningful messages for your commits.

:::::::::::::::::::::::::::::::::::::::::  callout
If you are working with Python version >= 3.13,  the git output may differ from what we've described above.
venvs created with python -m venv include a .gitignore by default so venv will not show up in version control. 

This .gitignore inside venv/ contains a `*` line:

This tells Git to ignore everything in that folder, so you don’t accidentally commit the virtual environment to your repository.

:::::::::::::::::::::::::::::::::::::::::