Changes by Ned Deily n...@acm.org:
--
nosy: +ncoghlan
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20417
___
___
Python-bugs-list mailing list
Nick Coghlan added the comment:
As Donald notes, this was explicitly covered in the PEP: the onus is on the
distros to make ensurepip and pyvenv work in a way that complies with their
debundling requirements (e.g. by using rewheel, or redirecting to the system
installer).
The
Arfrever Frehtes Taifersar Arahesis added the comment:
Some distributions have policies about not bundling external code.
ensurepip currently bundles some versions of setuptools and pip.
--
___
Python tracker rep...@bugs.python.org
Donald Stufft added the comment:
Yes I am aware of that. However ensurepip is also required to maintain
functionality of the venv module in 3.4. See the guidelines in
http://www.python.org/dev/peps/pep-0453/#recommendations-for-downstream-distributors
which explicitly mentions the fact that
New submission from Arfrever Frehtes Taifersar Arahesis:
ensurepip should not be installed when --without-ensurepip was passed to
configure.
I attach the patch.
--
assignee: dstufft
components: Installation
files: ensurepip_installation.patch
keywords: patch
messages: 209536
nosy:
Donald Stufft added the comment:
I don't see any reason not to install ensurepip in this situation. That flag
controls whether or not ``python -m ensurepip`` will be executed during the
install, but ensurepip itself will still be installed. It is not an optional
module
--
