removed implementation details and more info on Requires-Dist vs Require
This commit is contained in:
parent
9065202902
commit
a97586edfe
10
pep-0386.txt
10
pep-0386.txt
|
@ -26,9 +26,10 @@ current users, such as PyPI usually consider the latest version pushed as the
|
|||
`latest` one, regardless of the expected semantics.
|
||||
|
||||
Distutils will soon extend its capabilities to allow distributions to express a
|
||||
dependency on other distributions through the `Requires-Dist` metadata field
|
||||
dependency on other distributions through the ``Requires-Dist`` metadata field
|
||||
(see PEP 345 [#pep345]_) and it will optionally allow to use that field to
|
||||
restrict the dependency to a set of compatible versions.
|
||||
restrict the dependency to a set of compatible versions. Notice that this field
|
||||
is replacing ``Requires`` that was expressing dependencies on modules and packages.
|
||||
|
||||
The ``Requires-Dist`` field will allow a distribution to define a dependency on
|
||||
another package and optionally restrict this dependency to a set of
|
||||
|
@ -346,11 +347,6 @@ Or compared with others::
|
|||
A class method called ``from_parts`` is available if you want to create an
|
||||
instance by providing the parts that composes the version.
|
||||
|
||||
Each part is a tuple and there are three parts:
|
||||
|
||||
- the main version part
|
||||
- the pre-release part
|
||||
|
||||
Examples ::
|
||||
|
||||
>>> version = RationalVersion.from_parts((1, 0))
|
||||
|
|
Loading…
Reference in New Issue