Hi,
I wonder what you think about splitting out pip and setuptools from python3 package.
http://bugs.alpinelinux.org/issues/5381
I think I would like to do this, because it saves space and I think its
the best technical way to do it. But it also means that we need to add
py3-setuptools as makedepends on a lot of packages, and it may break
things for docker users who apk add python3 && pip install ...
Do you think it is worth it?
I think it is.
-nc
---
Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org
Help: alpine-devel+help@lists.alpinelinux.org
---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 27/10/17 11:37, Daniel Isaksen wrote:
> I would like to do this as well, as setuptools and pip aren't a> part of "core python". It will also, as you said, save disk space.https://docs.python.org/3/installing/index.html
"pip is the preferred installer program. Starting with Python 3.4, it
is included by default with the [official] Python binary."
On 27/10/2017 11:33, Natanael Copa wrote:
> I think I would like to do this, because it saves space and I think> its the best technical way to do it. But it also means that we need> to add py3-setuptools as makedepends on a lot of packages, and it> may break things for docker users who apk add python3 && pip> install ...> > Do you think it is worth it?
The interpreter will work against you, especially if people do not
know that py3-setuptools contains pip (or would it be py3-pip?) –
since the official Python distribution contains pip now, for distros
that remove it they have added "python3 -m ensurepip" which will go
fetch pip from the Internet (if a network connection is available).
Personally, I feel like this would be a waste of effort. However, if
a split really is needed/desired, then I strongly suggest py3-pip as a
separate package from py3-setuptools so that people can find and
install pip easily.
Please additionally note that while the original bug report says to
remove 'ensurepip', the PEP linked in the bug report clearly states:
> Even if pip is made available globally by other means, do not> remove the ensurepip module in Python 3.4 or later. ensurepip will> be required for automatic installation of pip into virtual> environments by the venv module.
This is very important for reproduceable environments and is
frequently used in regression testing environments. Breaking `venv`
is not worth 1.6 MiB disk; please do not remove the ensurepip module.
Best,
- --arw
- --
A. Wilcox (awilfox)
Project Lead, Adélie Linux
http://adelielinux.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJZ827XAAoJEMspy1GSK50U120P/06XeKG87kH0g7SXhGeP6UXP
nVnQ2ogHR4yOt0sl9ebB8zSNULri2h1GMAEOMIvoKNco5LN6pAFv+JRBaK0QNNd8
KZjUUyBk0n7svmhWOWmQrChK7pgMTqftDJTy4jys5YAoQBLuxzV1K/03wiMYnTZp
I6bsGJ/KpFUdfW5cfKIKXMYOpkkSK5fIDEwFDKgOf2g5U15cubou4KCCOZrBThEv
4jlIXzFZoRj8D1LM1TtSkrBdc16/GVtnnRWYx4vafMXlmJW18q0vjfN1vfBatqYH
YaItd8BYrvaOhLmpYgtHxf9q7qBZPBG9T7fwj4iYPeOj9viCHVYvfX4QEU6GPvTB
LyS2p7Q2F4+H9u6rNuAphfT0LmAVDBGsrxsmp7zvt6B+rTavfzMAhIbpAwEKiKRh
Vc1t1ThH9r6xSQwLTek8vvwf5ARb4WnJO0RUYF8xzW5egyz1xp6QhMEgev1Kj5tH
9pAzL5BslJ+B9gbhqNQ0f70uu8zPESHHKvBVGMJjPm08OB7Kx5IEgcCee73O/kiy
zeeS4g+RJ3UW/90UWOw/i2uLdrqlhvdpQbEBCeEAqPdshl+TblrN/1V+ZwWiZiTg
kYbce/wL8mL1xZ1A49wzaPlaGmH5ufqzmd3hVqsp8n2SjSYWI38S++CnfT//KzOp
jd7H0XYPeyUifjY8KMFr
=dE0k
-----END PGP SIGNATURE-----
---
Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org
Help: alpine-devel+help@lists.alpinelinux.org
---
I would like to do this as well, as setuptools and pip aren't a part of
"core python". It will also, as you said, save disk space.
It's kind of what npm is to Node.js, although they're usually packaged
together.
If someone is willing to put the effort into this, I'd say it's worth it.
- Daniel
On Fri, Oct 27, 2017 at 6:33 PM, Natanael Copa <ncopa@alpinelinux.org>
wrote:
> Hi,>> I wonder what you think about splitting out pip and setuptools from> python3 package.>> http://bugs.alpinelinux.org/issues/5381>> I think I would like to do this, because it saves space and I think its> the best technical way to do it. But it also means that we need to add> py3-setuptools as makedepends on a lot of packages, and it may break> things for docker users who apk add python3 && pip install ...>> Do you think it is worth it?>> I think it is.>> -nc>>> ---> Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org> Help: alpine-devel+help@lists.alpinelinux.org> --->>
Hello,
On 10/27/2017 06:33 PM, Natanael Copa wrote:
> Hi,>> I wonder what you think about splitting out pip and setuptools from python3 package.>> http://bugs.alpinelinux.org/issues/5381>> I think I would like to do this, because it saves space and I think its> the best technical way to do it. But it also means that we need to add> py3-setuptools as makedepends on a lot of packages, and it may break> things for docker users who apk add python3 && pip install ...>> Do you think it is worth it?>> I think it is.
Yes and no. Considering the venv issue mentioned by awilfox it might
cause more issues that it's worth actually. Since Alpine might be
heavily used in reproducible environments and other testing stuff I'd
like to keep ensurepip.
However, splitting pip into py3-pip would be nice.
What do you think?
--scadu
---
Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org
Help: alpine-devel+help@lists.alpinelinux.org
---
Hi
On Fri, Oct 27, 2017 at 12:37:31PM -0500, A. Wilcox wrote:
> The interpreter will work against you, especially if people do not> know that py3-setuptools contains pip (or would it be py3-pip?) –
I am skeptic, too. I know I used distros that had setuptools split,
but if you do anything with python you more less always need pip,
alpine can't possible support the vast python-eco-system.
Having said that, if we decide to split setuptools, I would help.
Best,
Jean-Louis