Other references/usages of poetry migrated to uv

3 files changed, 5 insertions, 5 deletions

diff --git a/pydis_site/apps/content/resources/guides/pydis-guides/contributing/bot-extended-configuration-options.md b/pydis_site/apps/content/resources/guides/pydis-guides/contributing/bot-extended-configuration-options.md
index f5425d88..b35c202d 100644
--- a/pydis_site/apps/content/resources/guides/pydis-guides/contributing/bot-extended-configuration-options.md
+++ b/pydis_site/apps/content/resources/guides/pydis-guides/contributing/bot-extended-configuration-options.md
@@ -140,9 +140,9 @@ With at least the site running in Docker already (see the previous section on ho
         <div class="card-content">
             Notice that the bot is started as a module. There are several ways to do so:
             <ul>
-                <li>Through the command line, inside the bot directory, with either <code>poetry run task start</code>, or directly <code>python -m bot</code>.</li>
+                <li>Through the command line, inside the bot directory, with either <code>uv run task start</code>, or directly <code>python -m bot</code>.</li>
                 <li>If using PyCharm, enter <code>Edit Configurations</code> and set everything according to this image: <img src="/static/images/content/contributing/pycharm_run_module.png"></li>
-                <li>If using Visual Studio Code, set the interpreter to the poetry environment you created. In <code>launch.json</code> create a new Python configuration, and set the name of the program to be run to <code>bot</code>. VSC will correctly run it as a module.</li>
+                <li>If using Visual Studio Code, set the interpreter to the uv environment you created. In <code>launch.json</code> create a new Python configuration, and set the name of the program to be run to <code>bot</code>. VSC will correctly run it as a module.</li>
             </ul>
         </div>
     </div>
diff --git a/pydis_site/apps/content/resources/guides/pydis-guides/contributing/linting.md b/pydis_site/apps/content/resources/guides/pydis-guides/contributing/linting.md
index b634f513..3ef3b05c 100644
--- a/pydis_site/apps/content/resources/guides/pydis-guides/contributing/linting.md
+++ b/pydis_site/apps/content/resources/guides/pydis-guides/contributing/linting.md
@@ -11,4 +11,4 @@ If the linter complains, the commit is aborted so that you can fix the linting e
 That way, you never commit the problematic code in the first place!
 
 Please refer to the project-specific documentation to see how to setup and run those tools.
-In most cases, you can install pre-commit using `poetry run task precommit`, and lint using `poetry run task lint` in the console.
+In most cases, you can install pre-commit using `uv run task precommit`, and lint using `uv run task lint` in the console.
diff --git a/static-builds/README.md b/static-builds/README.md
index afd34bb0..8eed267e 100644
--- a/static-builds/README.md
+++ b/static-builds/README.md
@@ -17,9 +17,9 @@ They are split into two parts:
 To get started with building, you can use the following command:
 
 ```shell
-poetry install
+uv sync
 python -m pip install httpx==0.19.0
-poetry run task static
+uv run task static
 ```
 
 Alternatively, you can use the [Dockerfile](/Dockerfile) and extract the build.