From 32f4aecd9d8b4b834add4b16599a34d7a9801761 Mon Sep 17 00:00:00 2001 From: Bradley Reynolds Date: Sun, 7 Dec 2025 15:53:00 -0600 Subject: [PATCH] venv tag: only suggest invoking Python with `py` The `python` command on Windows is being phased out. --- bot/resources/tags/venv.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bot/resources/tags/venv.md b/bot/resources/tags/venv.md index bf0158fdeb..3074465106 100644 --- a/bot/resources/tags/venv.md +++ b/bot/resources/tags/venv.md @@ -6,7 +6,7 @@ embed: Virtual environments are isolated Python environments, which make it easier to keep your system clean and manage dependencies. By default, when activated, only libraries and scripts installed in the virtual environment are accessible, preventing cross-project dependency conflicts, and allowing easy isolation of requirements. -To create a new virtual environment, you can use the standard library `venv` module: `python3 -m venv .venv` (replace `python3` with `python` or `py` on Windows) +To create a new virtual environment, you can use the standard library `venv` module: `python3 -m venv .venv` (replace `python3` with `py` on Windows) Then, to activate the new virtual environment: