PEP 453: alternate installer wording tweak
Avoid implying that hashdist and conda are part of the same project.
This commit is contained in:
parent
0851a088fc
commit
f5dae2a3d7
10
pep-0453.txt
10
pep-0453.txt
|
@ -133,12 +133,10 @@ feature release cycle, instead of using the general difficulty of installing
|
||||||
third-party packages as justification for inclusion.
|
third-party packages as justification for inclusion.
|
||||||
|
|
||||||
Providing a standard installation system also helps with bootstrapping
|
Providing a standard installation system also helps with bootstrapping
|
||||||
alternate build and installer systems, such as ``setuptools``,
|
alternate build and installer systems, such as ``zc.buildout``, ``hashdist``
|
||||||
``zc.buildout`` and the ``hashdist``/``conda`` combination that is aimed
|
and ``conda``. So long as ``pip install <tool>`` works, then a standard
|
||||||
specifically at the scientific community. So long as
|
Python-specific installer provides a reasonably secure, cross platform
|
||||||
``pip install <tool>`` works, then a standard Python-specific installer
|
mechanism to get access to these utilities.
|
||||||
provides a reasonably secure, cross platform mechanism to get access to
|
|
||||||
these utilities.
|
|
||||||
|
|
||||||
|
|
||||||
Enabling the evolution of the broader Python packaging ecosystem
|
Enabling the evolution of the broader Python packaging ecosystem
|
||||||
|
|
Loading…
Reference in New Issue