From c188b11b0ab5e08521ff38291b169bd1ea45069e Mon Sep 17 00:00:00 2001 From: Charlie Marsh Date: Tue, 19 Nov 2024 16:41:30 -0500 Subject: [PATCH] Fix typo in PyTorch docs (#9249) ## Summary Raised at https://x.com/stefanofusai/status/1858981714942718163/photo/1. --- docs/guides/integration/pytorch.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/guides/integration/pytorch.md b/docs/guides/integration/pytorch.md index 485f314b2..89eb51385 100644 --- a/docs/guides/integration/pytorch.md +++ b/docs/guides/integration/pytorch.md @@ -15,8 +15,8 @@ CUDA). From a packaging perspective, PyTorch has a few uncommon characteristics: - Many PyTorch wheels are hosted on a dedicated index, rather than the Python Package Index (PyPI). - As such, installing PyTorch typically often configuring a project to use the PyTorch index. -- PyTorch includes distinct builds for each accelerator (e.g., CPU-only, CUDA). Since there's no + As such, installing PyTorch often requires configuring a project to use the PyTorch index. +- PyTorch produces distinct builds for each accelerator (e.g., CPU-only, CUDA). Since there's no standardized mechanism for specifying these accelerators when publishing or installing, PyTorch encodes them in the local version specifier. As such, PyTorch versions will often look like `2.5.1+cpu`, `2.5.1+cu121`, etc.