From b06ee87b0a3e013cec917b41373f11a55989b9d3 Mon Sep 17 00:00:00 2001 From: David Shrewsbury Date: Wed, 21 Aug 2024 12:48:38 -0400 Subject: [PATCH] Fix doc errors in 3.1 porting guide --- docs/porting_guides/porting_guide_v3.1.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/porting_guides/porting_guide_v3.1.rst b/docs/porting_guides/porting_guide_v3.1.rst index fc162f81..b22d5d8a 100644 --- a/docs/porting_guides/porting_guide_v3.1.rst +++ b/docs/porting_guides/porting_guide_v3.1.rst @@ -26,10 +26,10 @@ Builder will *expect* the requirements file to be in this format, but it makes t #. Comments (lines beginning with ``#``) are ignored. #. Any line from the requirements file that is not compliant with PEP508 causes a warning to be emitted and - the line passed through to ``pip`` unmodified. It is not recommended to depend on this behavior, as we + the line passed through to ``pip`` unmodified. It is not recommended to depend on this behavior, as it can change suddenly between ``pip`` releases, and can cause other problems with dependency resolution. -The passthrough of non-PEP508 compliant lines may expose issues that were hidden by the, +The passthrough of non-PEP508 compliant lines may expose issues that were hidden by the version 3.0 dependency sanitizer, which often silently ignored and removed them. Dependency Sanitization