iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 440: Remove references to PEP 426 

PEP 426 is still in draft, and is likely to stay that
way for quite some time. This update removes those
references, and instead includes the relevant details
directly in PEP 440.
This commit is contained in:
Nick Coghlan 2016-01-21 16:15:12 +10:00
parent 7c2c1021ef
commit a3519cb25f
1 changed files with 31 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

44
pep-0440.txt
View File

@ -34,17 +34,36 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119.
The following terms are to be interpreted as described in PEP 426:
"Projects" are software components that are made available for integration.
Projects include Python libraries, frameworks, scripts, plugins,
applications, collections of data or other resources, and various
combinations thereof. Public Python projects are typically registered on
the `Python Package Index`_.
* "Distributions"
* "Releases"
* "Build tools"
* "Index servers"
* "Publication tools"
* "Installation tools"
* "Automated tools"
* "Projects"
"Releases" are uniquely identified snapshots of a project.
"Distributions" are the packaged files which are used to publish
and distribute a release.
"Build tools" are automated tools intended to run on development systems,
producing source and binary distribution archives. Build tools may also be
invoked by integration tools in order to build software distributed as
sdists rather than prebuilt binary archives.
"Index servers" are active distribution registries which publish version and
dependency metadata and place constraints on the permitted metadata.
"Publication tools" are automated tools intended to run on development
systems and upload source and binary distribution archives to index servers.
"Installation tools" are integration tools specifically intended to run on
deployment targets, consuming source and binary distribution archives from
an index server or other designated location and deploying them to the target
system.
"Automated tools" is a collective term covering build tools, index servers,
publication tools, integration tools and any other software that produces
or consumes distribution version and dependency metadata.
Version scheme
==============
@ -1084,9 +1103,8 @@ uploaded distributions. Direct references are intended as a tool for
software integrators rather than publishers.
Depending on the use case, some appropriate targets for a direct URL
reference may be a valid ``source_url`` entry (see PEP 426), an sdist, or
a wheel binary archive. The exact URLs and targets supported will be tool
dependent.
reference may be an sdist or a wheel binary archive. The exact URLs and
targets supported will be tool dependent.
For example, a local source archive may be referenced directly::
@ -1525,7 +1543,7 @@ justifications for needing such a standard can be found in PEP 386.
https://github.com/pypa/packaging/blob/master/tasks/check.py
.. [3] Pessimistic version constraint
http://guides.rubygems.org/patterns/
http://docs.rubygems.org/read/chapter/16
.. [4] File URIs in Windows
http://blogs.msdn.com/b/ie/archive/2006/12/06/file-uris-in-windows.aspx