> While I understand what you're trying to achieve (and I'm in favour, > in general) it should be remembered that pip's core goal is installing > packages - not being a component of a development workflow.
Yes -- clear separation of concerns here! So what IS supposed to be used in the development workflow? The new mythical build system? This brings. me back to my setuptools-lite concept -- while we are waiting for a new build system, you can use setuptools-lite, and get a setup.py install or setup.py develop that does what it's supposed to do and nothing else.... OK, I'll go away now :-) -Chris > We absolutely need to make pip useful in the development workflow type > of situation (that's why pip install -e exists, after all). But I > don't think it's so much pip "trying to be too clever" as incremental > rebuilds wasn't the original use case that "pip install ." was > designed for. What we'll probably have to do is be *more* clever to > special case out the situations where a development-style support for > incremental rebuilds is more appropriate than the current behaviour. > > Paul > _______________________________________________ > Distutils-SIG maillist - Distutils-SIG@python.org > https://mail.python.org/mailman/listinfo/distutils-sig _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
