> I'm confident we're > going to want a "support prebuilt wheels only" installation option > downstream in the Linux distro world - Interesting-- so move to a Python specific binary distribution option -- rather than using rm or deb packages? Doesn't lead to a dependency heck? I.e no way to express non-python dependencies? And while we are moving forward, can we please deprecate dependency management and installation from setuptools? Is there a philosophy of intended separation of concerns articulated somewhere? -Chris > shipping setuptools by default > is a pragmatic concession to practical reality rather than something > we *want* to be doing. > > As such, I do think Robert raises a good point that any new ensurepip > option should probably prevent installation of both wheel *and* > setuptools, since pip can install from wheel files without setuptools > these days. The CLI option name might be something like > "--no-build-tools", and could also be added to the public pyvenv and > virtualenv interfaces. > > Downstream in Fedora, now that we have weak dependency support, I'd > advocate for switching the python->setuptools dependency over to > Recommends, and adding wheel as a Recommends dependency from the > start. > > Cheers, > Nick. > > -- > Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/chris.barker%40noaa.gov
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4