This commit resolves all outstanding duplicate label
and duplicate citation warnings.
I have not yet addressed unreferenced footnote warnings.
I took the general strategy of replacing a target above a section heading
with references directly to that section heading,
or where impractical, disambiguting the target with ``PEP NNN``.
I also converted all the citations in PEP 482 to links,
as they were causing duplicate citation warnings.
* PEP 394: Distributions can choose what does python mean
Co-Authored-By: Petr Viktorin <encukou@gmail.com>
* fixup! PEP 394: Distributions can choose what does python mean
* fixup! PEP 394: Distributions can choose what does python mean
* fixup! PEP 394: Distributions can choose what does python mean
* PEP 394: Keep version agnostic shebang recommendation
This update reverts back to the version agnostic "python" invocation
as the default recommendation for developers, and rewords the
rest of the PEP accordingly.
In particular, it makes it clear that publishers are free to adopt
the attitude of "we assume you are using a virtual environment",
while at the same time granting the distributors the freedom they
need to make software with the expectation work correctly when
run directly against a system Python installation.
* Apply suggestions from code review
Co-Authored-By: Carol Willing <carolcode@willingconsulting.com>
* Moving letters around
* Change the abstract
* Remove a paragraph
* ValueError: some authors have more than one email address listed
* Apply suggestions from code review
Co-Authored-By: Petr Viktorin <encukou@gmail.com>
* Address review comments
* Rename section headers
* Push script publishers and users to virtual environments
* Rewording
* Remove "preferred" shebang line wording
* Change post date
* Little tweaks
* Address review comments
- Clarify wording on "older" Linux distros
- Remove discussion aroung Python 4.0
* Allow the `python` command to not be installed, and other minor edits
- Distributions can omit the ``python`` command even when
``python2`` is installed in test environments, build systems,
and other controlled environments where being explicit is
valued more than user experience.
- Users, by a deliberate action, change
``python`` to invoke Python 3. Activating a venv counts as
such an action.
- Other edits and clarifications
* Add myself as an author
Adam Turner
Miro Hrončok
Nick Coghlan
Petr Viktorin
Mariatta
Huang Huang
Benjamin Peterson
Barry Warsaw
Berker Peksag
Martin v. Löwis