On 22 October 2015 at 12:59, Chris Barker <chris.bar...@noaa.gov> wrote: > On Wed, Oct 21, 2015 at 4:52 PM, Robert Collins <robe...@robertcollins.net> > wrote: >> >> > Hmm, now that I think about it, maybe I can just banish setuptools from >> > my >> > setup.py, stick with distutils, and then make sure to use pip to >> > actually >> > invoke anything -- so it will inject setuptools, but only use the bits >> > we >> > need.... >> > >> > I'll have to try that..... >> >> You won't gain anything from that. distutils doesn't track installed >> files either. You *must* use 'pip install .' or 'setup.py bdist_wheel' >> + 'pip install .' with the current ecosystem state, > > > I guess I wasn't clear -- the idea was to force myself to use pip install, > rather than ever doing a plain > > setup.py install or > setup.py develop > > so: > pip install ./ > or > pip install -e ./ > > this way, pip will inject the parts of setuptools I really need, but > hopefully not any other cruft.
Its precisely the same as doing """ import setuptools from distutils import setup ... setup() """ Except that other people may still run setup.py directly, and then you'll be picking up the pieces :). -Rob -- Robert Collins <rbtcoll...@hp.com> Distinguished Technologist HP Converged Cloud _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
