@@ -21,11 +21,11 @@ For each dependency, there can be a version "requirement" that can be an
2121exact version, a version expression (aka. version specifier) as defined
2222in `pep-0440 <https://www.python.org/dev/peps/pep-0440/ >`__
2323with additional OS and environment tags and constraints as specified in
24- `pep-0508 <https://www.python.org/dev/peps/pep-0508/ >`__ .
24+ `pep-0508 <https://www.python.org/dev/peps/pep-0508/ >`__ .
2525
26- In particular the required Python version of a package (or version specifier)
27- can be set for the whole package (with the``python_requires`` attribute) or as
28- a marker for a given direct or indirect dependency. pip processes requirement
26+ In particular the required Python version of a package (or version specifier)
27+ can be set for the whole package (with the``python_requires`` attribute) or as
28+ a marker for a given direct or indirect dependency. pip processes requirement
2929specifiers and constraints from a "requirements" file and internally resolves
3030dependency versions recursively by querying the PyPI Python package
3131index repository at https://PyPI.org
@@ -129,7 +129,7 @@ And a flat list of unique dependencies would be:
129129- thing 3.0
130130- shebang 1.0
131131
132- The implementation may likely be similar to
132+ The implementation may likely be similar to
133133`pipgrip <https://github.com/ddelange/pipgrip >`__,
134134but using the `resolvelib <https://github.com/sarugaku/resolvelib >`__
135135library as used and vendored in pip instead of an implementation of
@@ -139,7 +139,7 @@ The expected benefit of this tool is a simpler way to resolve Python
139139dependencies that will not require complex installation of a Python toolchain
140140specific to a given project environment when the goal is only to resolve
141141dependencies. In particular the key new capability is to run this tool on a
142- single Python version and resolve versions for alternative Python versions,
142+ single Python version and resolve versions for alternative Python versions,
143143operating systems and architectures without having to install all the packages
144144in the dependency tree.
145145
@@ -158,7 +158,8 @@ The outline of the processing is to:
158158- For each top-level requirement (e.g. name/version):
159159
160160 - Fetch all the corresponding versions metadata using the PyPI API(s)
161- - Fetch the packages as needed to further obtain the next-level dependencies, and this recursively
161+ - Fetch the packages as needed to further obtain the next-level
162+ dependencies, and this recursively
162163
163164- Resolve a correct dependency version for each name.
164165- Dump JSON
@@ -168,7 +169,7 @@ User experience:
168169----------------
169170
170171The goal of the command line interface and user experience is to be
171- obvious and familiar to a pip user.
172+ obvious and familiar to a pip user.
172173
173174Create a new CLI named "dad" short for "dad analyzes dependencies" with
174175these key options:
@@ -352,4 +353,3 @@ ScanCode Toolkit can detect the and normalize the declared licenses in package
352353metadata and also collect and normalize all the metadata. This could be
353354a refinement for later.
354355
355-
0 commit comments