PEP 366, 395, 413, 426, 430, 440, 531, 535, 3150: Fix footnotes (#2794)
This commit is contained in:
Hugo van Kemenade
GitHub
parent
38b778d3b9
commit
68160887c2
14
pep-0366.txt
14
pep-0366.txt
|
|
@ -103,7 +103,7 @@ which stored the main module's real module name in the
|
|||
``__module_name__`` attribute. It was reverted due to the fact
|
||||
that 2.5 was already in beta by that time.
|
||||
|
||||
Patch 1487 [4] is the proposed implementation for this PEP.
|
||||
Patch 1487 [4]_ is the proposed implementation for this PEP.
|
||||
|
||||
Alternative Proposals
|
||||
=====================
|
||||
|
|
@ -125,7 +125,7 @@ References
|
|||
==========
|
||||
|
||||
.. [1] Absolute/relative import not working?
|
||||
(https://bugs.python.org/issue1510172)
|
||||
(https://github.com/python/cpython/issues/43535)
|
||||
|
||||
.. [2] c.l.p. question about modules and relative imports
|
||||
(http://groups.google.com/group/comp.lang.python/browse_thread/thread/c44c769a72ca69fa/)
|
||||
|
|
@ -134,7 +134,7 @@ References
|
|||
(https://mail.python.org/pipermail/python-3000/2007-April/006793.html)
|
||||
|
||||
.. [4] PEP 366 implementation patch
|
||||
(http://bugs.python.org/issue1487)
|
||||
(https://github.com/python/cpython/issues/45828)
|
||||
|
||||
.. [5] Acceptance of the PEP
|
||||
(https://mail.python.org/pipermail/python-dev/2007-November/075475.html)
|
||||
|
|
@ -143,11 +143,3 @@ Copyright
|
|||
=========
|
||||
|
||||
This document has been placed in the public domain.
|
||||
|
||||
..
|
||||
Local Variables:
|
||||
mode: indented-text
|
||||
indent-tabs-mode: nil
|
||||
sentence-end-double-space: t
|
||||
fill-column: 70
|
||||
End:
|
||||
|
|
|
|||
24
pep-0395.txt
24
pep-0395.txt
|
|
@ -715,27 +715,19 @@ None as yet.
|
|||
References
|
||||
==========
|
||||
|
||||
.. [1] Module aliases and/or "real names"
|
||||
(https://mail.python.org/pipermail/python-ideas/2011-January/008983.html)
|
||||
.. [1] `Module aliases and/or "real names"
|
||||
<https://mail.python.org/pipermail/python-ideas/2011-January/008983.html>`__
|
||||
|
||||
.. [2] PEP 395 (Module aliasing) and the namespace PEPs
|
||||
(https://mail.python.org/pipermail/import-sig/2011-November/000382.html)
|
||||
.. [2] `PEP 395 (Module aliasing) and the namespace PEPs
|
||||
<https://mail.python.org/pipermail/import-sig/2011-November/000382.html>`__
|
||||
|
||||
.. [3] Updated PEP 395 (aka "Implicit Relative Imports Must Die!")
|
||||
(https://mail.python.org/pipermail/import-sig/2011-November/000397.html)
|
||||
.. [3] `Updated PEP 395 (aka "Implicit Relative Imports Must Die!")
|
||||
<https://mail.python.org/pipermail/import-sig/2011-November/000397.html>`__
|
||||
|
||||
.. [4] Elaboration of compatibility problems between this PEP and PEP 402
|
||||
(https://mail.python.org/pipermail/import-sig/2011-November/000403.html)
|
||||
* `Elaboration of compatibility problems between this PEP and PEP 402
|
||||
<https://mail.python.org/pipermail/import-sig/2011-November/000403.html>`__
|
||||
|
||||
Copyright
|
||||
=========
|
||||
|
||||
This document has been placed in the public domain.
|
||||
|
||||
..
|
||||
Local Variables:
|
||||
mode: indented-text
|
||||
indent-tabs-mode: nil
|
||||
sentence-end-double-space: t
|
||||
fill-column: 70
|
||||
End:
|
||||
|
|
|
|||
14
pep-0413.txt
14
pep-0413.txt
|
|
@ -593,7 +593,7 @@ resolving this becomes even more critical. While Mercurial phases may
|
|||
help to some degree, it would be good to eliminate the problem entirely.
|
||||
|
||||
One suggestion from Barry Warsaw is to adopt a non-conflicting
|
||||
separate-files-per-change approach, similar to that used by Twisted [2_].
|
||||
separate-files-per-change approach, similar to that used by Twisted [2]_.
|
||||
|
||||
Given that the current manually updated NEWS file will be used for the 3.3.0
|
||||
release, one possible layout for such an approach might look like::
|
||||
|
|
@ -914,19 +914,9 @@ References
|
|||
==========
|
||||
|
||||
.. [2] Twisted's "topfiles" approach to NEWS generation
|
||||
http://twistedmatrix.com/trac/wiki/ReviewProcess#Newsfiles
|
||||
https://web.archive.org/web/20120305142914/http://twistedmatrix.com/trac/wiki/ReviewProcess#Newsfiles
|
||||
|
||||
Copyright
|
||||
=========
|
||||
|
||||
This document has been placed in the public domain.
|
||||
|
||||
|
||||
..
|
||||
Local Variables:
|
||||
mode: indented-text
|
||||
indent-tabs-mode: nil
|
||||
sentence-end-double-space: t
|
||||
fill-column: 70
|
||||
coding: utf-8
|
||||
End:
|
||||
|
|
|
|||
21
pep-0426.txt
21
pep-0426.txt
|
|
@ -443,9 +443,9 @@ in Appendix A.
|
|||
Metadata validation
|
||||
-------------------
|
||||
|
||||
A `jsonschema <https://pypi.python.org/pypi/jsonschema>`__ description of
|
||||
A `jsonschema <https://pypi.org/project/jsonschema/>`__ description of
|
||||
the distribution metadata is `available
|
||||
<http://hg.python.org/peps/file/default/pep-0426/pydist-schema.json>`__.
|
||||
<https://hg.python.org/peps/file/default/pep-0426/pydist-schema.json>`__.
|
||||
|
||||
This schema does NOT currently handle validation of some of the more complex
|
||||
string fields (instead treating them as opaque strings).
|
||||
|
|
@ -1507,24 +1507,15 @@ Version 1.2 is specified in :pep:`345`.
|
|||
The initial attempt at a standardised version scheme, along with the
|
||||
justifications for needing such a standard can be found in :pep:`386`.
|
||||
|
||||
.. [1] reStructuredText markup:
|
||||
http://docutils.sourceforge.net/
|
||||
* `reStructuredText markup
|
||||
<https://docutils.sourceforge.io/>`__
|
||||
|
||||
.. _Python Package Index: http://pypi.python.org/pypi/
|
||||
.. _Python Package Index: https://pypi.org/
|
||||
|
||||
.. _TR39: http://www.unicode.org/reports/tr39/tr39-1.html#Confusable_Detection
|
||||
.. _TR39: https://www.unicode.org/reports/tr39/tr39-1.html#Confusable_Detection
|
||||
|
||||
|
||||
Copyright
|
||||
=========
|
||||
|
||||
This document has been placed in the public domain.
|
||||
|
||||
|
||||
..
|
||||
Local Variables:
|
||||
mode: indented-text
|
||||
indent-tabs-mode: nil
|
||||
sentence-end-double-space: t
|
||||
fill-column: 70
|
||||
End:
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ Background
|
|||
==========
|
||||
|
||||
With the transition of the overall Python ecosystem from Python 2 to Python 3
|
||||
still in progress, one question which arises periodically [1_, 2_] is when
|
||||
still in progress, one question which arises periodically [1]_, [2]_ is when
|
||||
and how to handle the change from providing the Python 2 documentation as
|
||||
the default version displayed at the docs.python.org root URL to providing
|
||||
the Python 3 documentation.
|
||||
|
|
@ -77,7 +77,7 @@ the path component.
|
|||
Proposal
|
||||
========
|
||||
|
||||
This PEP (based on an idea originally put forward back in May [3_]) is to
|
||||
This PEP (based on an idea originally put forward back in May [3]_) is to
|
||||
*not migrate* the Python 2 specific deep links at all, and instead adopt a
|
||||
scheme where all URLs presented to users on docs.python.org are qualified
|
||||
appropriately with the relevant release series.
|
||||
|
|
|
|||
53
pep-0440.txt
53
pep-0440.txt
|
|
@ -39,7 +39,7 @@ document are to be interpreted as described in :rfc:`2119`.
|
|||
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 <https://pypi.python.org>`__.
|
||||
the `Python Package Index <https://pypi.org/>`__.
|
||||
|
||||
"Releases" are uniquely identified snapshots of a project.
|
||||
|
||||
|
|
@ -762,7 +762,7 @@ specify the appropriate version order.
|
|||
|
||||
Specific build information may also be included in local version labels.
|
||||
|
||||
.. _Semantic versioning: http://semver.org/
|
||||
.. _Semantic versioning: https://semver.org/
|
||||
|
||||
|
||||
DVCS based version labels
|
||||
|
|
@ -1556,35 +1556,35 @@ References
|
|||
The initial attempt at a standardised version scheme, along with the
|
||||
justifications for needing such a standard can be found in :pep:`386`.
|
||||
|
||||
.. [1] Reference Implementation of PEP 440 Versions and Specifiers
|
||||
https://github.com/pypa/packaging/pull/1
|
||||
.. [2] `Version compatibility analysis script
|
||||
<https://github.com/pypa/packaging/blob/master/tasks/check.py>`__
|
||||
|
||||
.. [2] Version compatibility analysis script:
|
||||
https://github.com/pypa/packaging/blob/master/tasks/check.py
|
||||
.. [4] `File URIs in Windows
|
||||
<https://web.archive.org/web/20130321051043/http://blogs.msdn.com/b/ie/archive/2006/12/06/file-uris-in-windows.aspx>`__
|
||||
|
||||
.. [3] Pessimistic version constraint
|
||||
http://docs.rubygems.org/read/chapter/16
|
||||
.. [5] `Proof of Concept: PEP 440 within pip
|
||||
<https://github.com/pypa/pip/pull/1894>`__
|
||||
|
||||
.. [4] File URIs in Windows
|
||||
http://blogs.msdn.com/b/ie/archive/2006/12/06/file-uris-in-windows.aspx
|
||||
.. [6] `PEP440: foo-X.Y.Z does not satisfy "foo>X.Y"
|
||||
<https://mail.python.org/pipermail/distutils-sig/2014-December/025451.html>`__
|
||||
|
||||
.. [5] Proof of Concept: PEP 440 within pip
|
||||
https://github.com/pypa/pip/pull/1894
|
||||
.. [7] `PEP440: >1.7 vs >=1.7
|
||||
<https://mail.python.org/pipermail/distutils-sig/2014-December/025507.html>`__
|
||||
|
||||
.. [6] PEP440: foo-X.Y.Z does not satisfy "foo>X.Y"
|
||||
https://mail.python.org/pipermail/distutils-sig/2014-December/025451.html
|
||||
.. [8] `Amend PEP 440 with Wider Feedback on Release Candidates
|
||||
<https://mail.python.org/pipermail/distutils-sig/2014-December/025409.html>`__
|
||||
|
||||
.. [7] PEP440: >1.7 vs >=1.7
|
||||
https://mail.python.org/pipermail/distutils-sig/2014-December/025507.html
|
||||
.. [10] `PEP 440: regex should not permit Unicode [Nd] characters
|
||||
<https://github.com/python/peps/pull/966>`__
|
||||
|
||||
.. [8] Amend PEP 440 with Wider Feedback on Release Candidates
|
||||
https://mail.python.org/pipermail/distutils-sig/2014-December/025409.html
|
||||
* `Reference Implementation of PEP 440 Versions and Specifiers
|
||||
<https://github.com/pypa/packaging/pull/1>`__
|
||||
|
||||
.. [9] Changing the status of PEP 440 to Provisional
|
||||
https://mail.python.org/pipermail/distutils-sig/2014-December/025412.html
|
||||
* `Pessimistic version constraint
|
||||
<https://web.archive.org/web/20130509214125/http://docs.rubygems.org/read/chapter/16>`__
|
||||
|
||||
.. [10] PEP 440: regex should not permit Unicode [Nd] characters
|
||||
https://github.com/python/peps/pull/966
|
||||
* `Changing the status of PEP 440 to Provisional
|
||||
<https://mail.python.org/pipermail/distutils-sig/2014-December/025412.html>`__
|
||||
|
||||
Appendix A
|
||||
==========
|
||||
|
|
@ -1659,12 +1659,3 @@ Copyright
|
|||
=========
|
||||
|
||||
This document has been placed in the public domain.
|
||||
|
||||
|
||||
..
|
||||
Local Variables:
|
||||
mode: indented-text
|
||||
indent-tabs-mode: nil
|
||||
sentence-end-double-space: t
|
||||
fill-column: 70
|
||||
End:
|
||||
|
|
|
|||
16
pep-0531.txt
16
pep-0531.txt
|
|
@ -55,7 +55,7 @@ following characteristics:
|
|||
PEP Withdrawal
|
||||
==============
|
||||
|
||||
When posting this PEP for discussion on python-ideas [4_], I asked reviewers to
|
||||
When posting this PEP for discussion on python-ideas [4]_, I asked reviewers to
|
||||
consider 3 high level design questions before moving on to considering the
|
||||
specifics of this particular syntactic proposal:
|
||||
|
||||
|
|
@ -74,7 +74,7 @@ truth-checking "and" and "or" control flow operators were available?
|
|||
While the answers to the first question were generally positive, it quickly
|
||||
became clear that the answer to the second question is "No".
|
||||
|
||||
Steven D'Aprano articulated the counter-argument well in [5_], but the general
|
||||
Steven D'Aprano articulated the counter-argument well in [5]_, but the general
|
||||
idea is that when checking for "missing data" sentinels, we're almost always
|
||||
looking for a *specific* sentinel value, rather than *any* sentinel value.
|
||||
|
||||
|
|
@ -96,7 +96,7 @@ make sense, and it is accordingly withdrawn.
|
|||
|
||||
However, the discussion of the proposal did prompt consideration of a potential
|
||||
protocol based approach to make the existing ``and``, ``or`` and ``if-else``
|
||||
operators more flexible [6_] without introducing any new syntax, so I'll be
|
||||
operators more flexible [6]_ without introducing any new syntax, so I'll be
|
||||
writing that up as another possible alternative to :pep:`505`.
|
||||
|
||||
|
||||
|
|
@ -645,13 +645,3 @@ Copyright
|
|||
|
||||
This document has been placed in the public domain under the terms of the
|
||||
CC0 1.0 license: https://creativecommons.org/publicdomain/zero/1.0/
|
||||
|
||||
|
||||
..
|
||||
Local Variables:
|
||||
mode: indented-text
|
||||
indent-tabs-mode: nil
|
||||
sentence-end-double-space: t
|
||||
fill-column: 70
|
||||
coding: utf-8
|
||||
End:
|
||||
|
|
|
|||
12
pep-0535.txt
12
pep-0535.txt
|
|
@ -81,7 +81,7 @@ operations would be the same as the existing expansion for ``and``.
|
|||
Rationale
|
||||
=========
|
||||
|
||||
In ultimately rejecting :pep:`335`, Guido van Rossum noted [1_]:
|
||||
In ultimately rejecting :pep:`335`, Guido van Rossum noted [1]_:
|
||||
|
||||
The NumPy folks brought up a somewhat separate issue: for them,
|
||||
the most common use case is chained comparisons (e.g. A < B < C).
|
||||
|
|
@ -187,13 +187,3 @@ Copyright
|
|||
|
||||
This document has been placed in the public domain under the terms of the
|
||||
CC0 1.0 license: https://creativecommons.org/publicdomain/zero/1.0/
|
||||
|
||||
|
||||
..
|
||||
Local Variables:
|
||||
mode: indented-text
|
||||
indent-tabs-mode: nil
|
||||
sentence-end-double-space: t
|
||||
fill-column: 70
|
||||
coding: utf-8
|
||||
End:
|
||||
|
|
|
|||
51
pep-3150.txt
51
pep-3150.txt
|
|
@ -738,48 +738,37 @@ TO-DO
|
|||
References
|
||||
==========
|
||||
|
||||
.. [1] Explicitation lines in Python:
|
||||
https://mail.python.org/pipermail/python-ideas/2010-June/007476.html
|
||||
.. [1] `Explicitation lines in Python
|
||||
<https://mail.python.org/pipermail/python-ideas/2010-June/007476.html>`__
|
||||
|
||||
.. [2] 'where' statement in Python:
|
||||
https://mail.python.org/pipermail/python-ideas/2010-July/007584.html
|
||||
.. [2] `'where' statement in Python
|
||||
<https://mail.python.org/pipermail/python-ideas/2010-July/007584.html>`__
|
||||
|
||||
.. [3] Where-statement (Proposal for function expressions):
|
||||
https://mail.python.org/pipermail/python-ideas/2009-July/005132.html
|
||||
.. [3] `Where-statement (Proposal for function expressions)
|
||||
<https://mail.python.org/pipermail/python-ideas/2009-July/005132.html>`__
|
||||
|
||||
.. [4] Name conflict with NumPy for 'where' keyword choice:
|
||||
https://mail.python.org/pipermail/python-ideas/2010-July/007596.html
|
||||
.. [4] `Name conflict with NumPy for 'where' keyword choice
|
||||
<https://mail.python.org/pipermail/python-ideas/2010-July/007596.html>`__
|
||||
|
||||
.. [5] The "Status quo wins a stalemate" design principle:
|
||||
http://www.boredomandlaziness.org/2011/02/status-quo-wins-stalemate.html
|
||||
.. [6] `Assignments in list/generator expressions
|
||||
<https://mail.python.org/pipermail/python-ideas/2011-April/009863.html>`__
|
||||
|
||||
.. [6] Assignments in list/generator expressions:
|
||||
https://mail.python.org/pipermail/python-ideas/2011-April/009863.html
|
||||
.. [7] `Possible PEP 3150 style guidelines (#1)
|
||||
<https://mail.python.org/pipermail/python-ideas/2011-April/009869.html>`__
|
||||
|
||||
.. [7] Possible PEP 3150 style guidelines (#1):
|
||||
https://mail.python.org/pipermail/python-ideas/2011-April/009869.html
|
||||
.. [8] `Discussion of PEP 403 (statement local function definition)
|
||||
<https://mail.python.org/pipermail/python-ideas/2011-October/012276.html>`__
|
||||
|
||||
.. [8] Discussion of PEP 403 (statement local function definition):
|
||||
https://mail.python.org/pipermail/python-ideas/2011-October/012276.html
|
||||
.. [9] `Possible PEP 3150 style guidelines (#2)
|
||||
<https://mail.python.org/pipermail/python-ideas/2011-October/012341.html>`__
|
||||
|
||||
.. [9] Possible PEP 3150 style guidelines (#2):
|
||||
https://mail.python.org/pipermail/python-ideas/2011-October/012341.html
|
||||
* `The "Status quo wins a stalemate" design principle
|
||||
<https://www.curiousefficiency.org/posts/2011/02/status-quo-wins-stalemate.html>`__
|
||||
|
||||
.. [10] Multi-line lambdas (again!)
|
||||
https://mail.python.org/pipermail/python-ideas/2013-August/022526.html
|
||||
* `Multi-line lambdas (again!)
|
||||
<https://mail.python.org/pipermail/python-ideas/2013-August/022526.html>`__
|
||||
|
||||
Copyright
|
||||
=========
|
||||
|
||||
This document has been placed in the public domain.
|
||||
|
||||
|
||||
|
||||
..
|
||||
Local Variables:
|
||||
mode: indented-text
|
||||
indent-tabs-mode: nil
|
||||
sentence-end-double-space: t
|
||||
fill-column: 70
|
||||
coding: utf-8
|
||||
End:
|
||||
|
|
|
|||
Loading…
Reference in New Issue