Commit Graph

36 Commits

Author SHA1 Message Date
Mariatta cf3bad5ab3
Revert "Rename all .txt PEP files to .rst (GH-462)" (GH-464)
This reverts commit bb0e518ed3.
2017-11-11 11:28:55 -08:00
Huang Huang bb0e518ed3 Rename all .txt PEP files to .rst (GH-462)
For https://github.com/python/peps/issues/1
2017-11-11 10:30:43 -08:00
Ezio Melotti c245d58ca5 Add missing parenthesis (noticed by Jurko Gospodnetić). 2014-04-19 20:23:34 +03:00
Nick Coghlan 1838220d00 Fix PEP type for PEP 453 2013-12-21 22:44:18 +10:00
Barry Warsaw e66a71839b More PEP updates. 2013-11-22 12:30:31 -05:00
Nick Coghlan f5dae2a3d7 PEP 453: alternate installer wording tweak
Avoid implying that hashdist and conda are part of the same
project.
2013-10-26 15:51:53 +10:00
Nick Coghlan 4c8b5a26ff MvL accepted PEP 453! \o/ 2013-10-22 21:51:28 +10:00
Nick Coghlan d150e47692 PEP 453 postdate and wording tweaks 2013-10-20 22:20:53 +10:00
Nick Coghlan e83a58638e PEP 453 updates
- remove proposal to change the script installation directory on
  Windows due to the backwards incompatility issues pointed out
  by Paul Moore
- include an explicit requirement to resolve the requests
  certificate management issues prior to beta 2
- cleaner formatting of the integration timeline
2013-10-20 15:00:20 +10:00
Nick Coghlan 9fba6aeaad Tweak the proposed integration timeline 2013-10-15 22:43:46 +10:00
Nick Coghlan 92d4dbf0ec Add pip integration timeline to PEP 453
- timeline based on discussion with the 3.4 release team
  and the pip devs
- also clarified the two trust models on offer (i.e. that
  the PEP ensures trusting PyPI remains explicitly opt-in, just
  as it has always been in the past)
2013-10-15 22:33:12 +10:00
Nick Coghlan 8d82cbcca0 PEP 453 typo fix 2013-10-13 22:32:05 +10:00
Nick Coghlan e6cc2772ac PEP 453 post date and wording tweak 2013-10-13 22:27:37 +10:00
Nick Coghlan b6e2ec03f3 Additional PEP 453 fixes 2013-10-11 01:15:34 +10:00
Nick Coghlan 57ba690829 Revise PEP 453 to be docs-only for 2.7 & 3.3
- all functional changes are now 3.4 only
- still proposes docs changes for 2.7 & 3.3
- notes current effort to create a Windows installer for pip
- notes possibility of a future PEP to provide a combined
  CPython 2.7, pip and Python Launcher installer from python.org
2013-10-11 00:47:47 +10:00
Nick Coghlan 6482692ff6 More PEP 453 cleanups 2013-09-29 17:02:03 +10:00
Nick Coghlan d4fc58c7e7 PEP 453 typo 2013-09-29 16:37:32 +10:00
Nick Coghlan 2ce1f07c01 Minor PEP 453 tweaks
- link to latest discussion thread
- new post date
- typos
2013-09-29 16:25:12 +10:00
Nick Coghlan 75dcba1791 Additional rationale in PEP 453
I realised after the last round of reviews that a *big* chunk of the
rationale for this PEP was assumed knowledge on distutils-sig, and
this lead directly to the high rate of replies on python-dev that
just didn't get why the requested exemption to include the new
feature in Python 2.7.6 is so important.

The PEP now attempts to do a better job of bridging that gap, as
well as further expanding on how having the ``ensurepip`` module
fully public in older releases should actually make things *less*
confusing, rather than more, since it gives us a location to
explain the alternative fallback bootstrapping methods.
2013-09-29 15:15:43 +10:00
Nick Coghlan d3fef79eea PEP 453 updates
Combined update with changes from both Donald and I

- adjust the abstract to emphasise the fact this is first about
  recommending pip as the official installer, and only then
  about trying to ensure it is made readily available to users
- note in the rationale that this is a key stepping stone towards
  decoupling the release cycle of the language from that of the
  PyPI software distribution ecosystem
- expanded proposal overview (including explaining the logic that
  leads from recommending pip to providing it by default)
- note the benefit of being able to test the bootstrap using the
  existing buildbot fleet
- note the three known use cases for invoking ensurepip directly
- a little more detail on the required documentation updates
- be clear that easy_install *will* be installed by default, but
  that problem will go away once pip eliminates their setuptools
  dependency
- greatly expand on the rationale for including ensurepip in the
  2.7 and 3.3 maintenance releases, including an explanation of
  the origins of the current policy in the 2.2.x series, how the
  current proposal differs from those, and why this shouldn't
  open the floodgates to more requests for exemptions
- mention multiple commercial Python redistributors rather than
  just the one
- clarify various issues in the recommendations for downstream
  redistributors
- note the licenses for the bundled software
- explain rationale for not making this an installer-only change
  in 2.7 and 3.3
- explain rationale for keeping the ensurepip module public in
  2.7 and 3.3
- assorted cleanups to grammar and wording
2013-09-28 22:40:33 +10:00
Donald Stufft 98242cd315 Include macports and fink in the list of OSX installers 2013-09-23 20:15:21 -04:00
Nick Coghlan b8eea37bb9 PEP 453 post date and reference formatting 2013-09-23 21:07:30 +10:00
Nick Coghlan 3a9eb4ef0b PEP 453 updates
- use the module name Antoine suggested
- list the five distinct parts of the proposal when
  describing the implementation strategy
- note the bootstrap approach makes it easy to let people opt-out
- allow distros to redirect a global ensurepip invocation to the
  system package manager
- decide the open questions in favour of the currently documented
  approaches (i.e. no changes to uninstallation, update the
  directory layout and PATH handling on Windows)
2013-09-22 15:57:28 +10:00
Donald Stufft 49665d3360 Update PEP453 to address Debian's concerns and Antoine's 2013-09-19 10:14:02 -04:00
Donald Stufft 28b3bbec03 Add a new entry to Post-History 2013-09-19 09:23:03 -04:00
Donald Stufft 9d355e6f73 Minor changes to PEP453 for grammar and content 2013-09-19 09:22:19 -04:00
Nick Coghlan 70aa3a1a6b Added a second function to the API 2013-09-19 22:48:59 +10:00
Nick Coghlan b27a71809b Update PEP 453 based on MvL's feedback
- added a new security considerations section
- writing that made it clear it made more sense to just always
  install from the private copy, and leave all network access
  to the extracted pip
- this design change meant the original module name was no longer
  suitable, so it was changed to ``extractpip`` instead
- incorporated Van Lindberg's suggestion from a while back to
  rename Tools\Scripts on Windows to bin
2013-09-19 22:43:29 +10:00
Nick Coghlan 509af2ebae Update PEP 453 (pip bootstrapping)
- add MvL as BDFL-Delegate
- clarify that pip is made available by default
- miscellaneous updates to the rationale section
- include a rationale for choosing pip over other tools
- consolidate all the technical details under one heading
- be explicit about the proposed getpip.bootstrap API
- be explicit about the proposed venv API changes
- be explicit about the proposed installer semantics
- be explicit about the documentation impact
- restrict getpip additions to off-by-default security
  enhancements (enabled by the installers and pyvenv)
- clarify the Windows PATH is only modified when the relevant
  installer option is checked
- request that downstreams that *don't* provide pip at least properly
  document that fact
- avoid the term "bundled" (favouring "private copy" or "bootstrapped"
  as appropriate)
- name the Python Packaging Authority explicitly in the governance
  section and point out that umbrella group now also includes the PyPI
  and setuptools maintainers (and more) in addition to the original
  group of pip and virtualenv maintainers
- note the hassles CPython has had in the past regarding "externally
  maintained" modules
- note why we're not pursuing the idea of bootstrapping into the
  user site packages by default
2013-09-18 00:30:06 +10:00
Brett Cannon 027e281f27 Grammar touch-ups 2013-09-15 12:02:22 -04:00
Donald Stufft 4567850ee3 Update post history 2013-09-15 11:35:45 -04:00
Nick Coghlan e142f3e4a1 Add 3.3 and 2.7 back to pip boostrap PEP
Donald reminded me of both why we originally proposed that, and
how the current implementation supports older Python versions
2013-09-15 23:49:45 +10:00
Nick Coghlan 6a2614b488 Assorted PEP 453 (pip bootstrapping) updates
- revert to being explicitly 3.4 only (with rationale)
- open question re uninstallation
- open question re script execution on Windows
- explicit cover handling of the setuptools dependency
- spell out the proposed CLI options for getpip
- note that venv will also support --no-download
- explicitly note that pip may gain new features in CPython
  maintenance releases and continues using its own release
  cycle
- explicitly note that bundling pip doesn't preclude the
  use of alternate installers, but instead better *enables*
  them by making them easier to bootstrap
- note we should update to new pip version when they're
  released, so the release process just checks they're up to
  date.
2013-09-15 16:20:11 +10:00
Donald Stufft a426e80979 Update PEP453 for Grammar and add --without-pip to PyVenv 2013-08-30 11:45:51 -04:00
Donald Stufft ad3709035e Grammar fixes for PEP453 2013-08-30 09:38:12 -04:00
Nick Coghlan 50d7f5d693 Add PEP 453: explicit pip bootstrapping 2013-08-30 23:10:06 +10:00