-----Original Message----- From: Antonio Cavallo <antonio.cavallo.71@gmail.com> Sent: Sunday, January 27, 2019 5:05 PM To: Alex Walters <tritium-list@sdamon.com> Subject: Re: [Distutils] unifying package formats
I don't think they serve a much different scope after al:l both uncompress files under a filesystem. There are difference in the way .so/.dll are maintained/built and some ancillary metadata (and you can see commonality in between conda/pip as well) but that's about it.
Then, that puts 7-zip and the PYPA in the same scope. There is more to project and infrastructure scope than the technical scope of what the code is doing. No, pip's scope is strictly managing python packages, conda's scope is much wider than that.
On Sat, 26 Jan 2019 at 18:21, Alex Walters <tritium-list@sdamon.com <mailto:tritium-list@sdamon.com> > wrote:
-----Original Message----- From: Antonio Cavallo <antonio.cavallo.71@gmail.com <mailto:antonio.cavallo.71@gmail.com> > Sent: Saturday, January 26, 2019 6:01 PM To: distutils-sig@python.org <mailto:distutils-sig@python.org> Subject: [Distutils] unifying package formats
Hi, is there any initiative to share a common package format between conda and pip? They look very similar.
Thanks
They look similar, but they have very different scopes. Pip is for the python environment only. Conda acts more like a python focused, system- isolated APT. Unifying packaging for the general python ecosystem (wheels hosted on pypi installed with pip) with conda (full stack dependency management, including large quantities of foreign code) is likely to be impossible, and even if possible, impractical.