Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix doc errors in 3.1 porting guide #704

Merged
merged 1 commit into from
Aug 21, 2024
Merged

Fix doc errors in 3.1 porting guide #704

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/porting_guides/porting_guide_v3.1.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading